[WebKit-devel] Packaging for Debian

[Urs Wolfer]

On Friday 12 June 2009 18:25:07 Adrian von Bidder wrote:
> Heyho!

Hi

> I'm working on Debian packages for webkit-kde and the kpart, I'd appreciate
> if you could look at the following issues.
>
> CC:s appreciated, I don't read the list (I don't have the time to
> participate in the devlopment, so I'm just trying to help by allowing wider
> distribution and testing through the package.  I'll *try* to keep the
> package more or less up to date...)
>
> Ok, here's:
>
>  * svn://anonsvn.kde.org/home/kde/trunk/playground/libs/webkitkde contains
> the kpart and 3 shared libraries.  I have currently created a package for
> the libraries (with -dev and -dbg package) and a package for the kpart, but
> I'm not quite sure if that's the right thing.

It's okay.

> Do you view these libraries as integral part of the kpart with no external
> users?  If yes, I can probably just drop the library packages and not
> deliver the headers at all.

Some parts of KDE have an optional dependency to this code (e.g. KGet).
>
> Are external users of the libraries anticipated?  Or are they just a
> possibility?  Do you plan to maintain the ABI compatibility by changing the
> compatibility if the ABI changes?  And if you do so:  will you be managing
> the soname versions of the three libraries independently or will you lock
> the three libraries to always have the same (soname) version?  (If the
> versions will be maintained independently, I'll split the package into one
> per library.)

It's a possibility. As long as this code is in playground, no code/binary 
compatibility is guaranteed. Our plan is to move parts of the code (the libs 
part) into kdelibs at some point (hopefully soon). Starting from that point, 
full compatibility is guaranteed.
>
>  * linker flags:  Debian's library dependency scripts detected that webkit
> is probably linked unnecessarily against some libraries, see the warnings
> below.  How can I pass --as-needed to the linker to avoid these?  (They're
> libraries that are probably installed in any case due to other dependencies
> in KDE so it's not a bad problem, but I'd really like to keep my
> dependencies as clean as possible.)  Passing -DCMAKE_LD_FLAGS=... seems to
> be ignored or overridden.

No idea what flag you can pass. But if you can cleanup our dependencies, I'm 
happy to commit your patch to SVN.


>  * And finally, to satisfy my own curiosity as well as for adding it to my
> cautionary note in the package's README file:  Is there a roadmap on
> when/at what milestones webkitkde will be released from playground to a
> "real" version?

There is no real schedule. Please see http://techbase.kde.org/Projects/WebKit 
for more information.

> The package is currently waiting in Debian's NEW processing and is
> available from http://fortytwo.ch/debian/webkitkde (source and binary
> package) or https://fortytwo.ch/hg/pkg-webkitkde (mercurial repository) in
> the mean time.  (It is compiled against Debian unstable/sid.)

Thanks for creating the package for debian :)

Bye
urs
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part.
Url : http://mail.kde.org/pipermail/webkit-devel/attachments/20090613/7ede041d/attachment.sig