[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Packaging:library packaging stuff

On 2009-06-08, Adrian von Bidder <avbidder@fortytwo.ch> wrote:
>  * how can I build the dependencies of the -dev package in a sane way?  I'm=
> sure creating them by hand is not optimal.  (And I'm sure I've read at some=

You need to create it by hand by looking at what includes is in *your*
public headers.

> time how to refer to my own version properly for the dependency of lib-dev=
>=2D> lib, but I can't find it right now.)

Depends: libfoo1 (= ${binary:Version})
And talking about depens, why is the dependency between the kpart
packkage and teh library package unversioned ?

>  * after installing a KDE plug-in: is my guess correct that I can't really=
> call kbuildsyocca4 since it needs to be called as user, not root?

kded4 has a kdirwatch (inotify) watching the relevant dirs and runs
kbuildsycoca4 as user when needed. It is also run on kde login.

>  * should I create a -dbg package?  I've just included the debugging info i=
> n=20
>=2Ddev right now since it's a small library, but I'm not quite sure.

You at least need to get the -dbg package's dependencies right (by
hand). My guess would be it needs kdelibs5-dbg and libqt4-webkit-dbg,
else the backtrace will probably be of not much use.

>  * How do I pass the right linker flags (-Wl,--as-needed?) through cmake to=
> the linker?  Whatever I tried so far, it was ignored and I get a few=20
> warnings from dpkg-shlibdeps.  (This is more a question of style, since=20
> they're libraries I'd expect a KDE user has installed in any case.)

-DCMAKE_LD_FLAGS="-Wl,--as-needed -Wl,-z,defs".

Unless you know what you are doing, don't pass --as-needed with out

And you should not unless you really know why put the SOVERSION in the
-dev package.

I'm not sure that konq-plugin-webkit is a good package name, as I'm
pretty sure it is not specific to konqueror in any way, but a more
generic webkit based kpart.

Unless you know that all libraries *will* change their ABI at the same
time, you should not put several libraries in the same package.

I so far haven't looked at anything but your email and the overview here


Reply to: