On Monday 22 August 2005 23:38, Kurt Roeckx wrote:
[Sorry for my (too) late response. Just returned from holidays.]
> Package: digikam
> Version: 0.7.4-1
> Severity: serious
>
> Hi,
>
> Your package has a shared library in it: /usr/lib/libdigikam.so
Hi Kurt,
technically it's a shared library, but it was never intented to
be used as a library for others by upstream! It's just a container
to share code as needed between digikam, showfoto (pkg digikam) and
digikamplugins. And this code changes continuesly!!
> You need to split the package so that the symlink and headers and
> things like that are in a -dev package that depends on the
> package with the lib in it. Other package like
> digikamimageplugins will then need to build-depend on the -dev
> package.
That makes no sense IMHO as upstream changes contents and breaks
API and ABI as needed. This happened with every minor release
in the 0.6.*, 0.7.* and upcoming 0.8 release (exception 0.7.4 which
was an translation & documentation update)
> Please see things like the debian policy (section 8, 10.2) and
> maybe the Debian Library Packaging guide.
Before 0.7 pkging I spend quite some time reading them both
(and FHS) with respect to this lib/-dev stuff. None of the
advantages and needs for the split apply is this case.
As I wrote, there's no API or ABI promise. It's just a
container to share code between tighly coupled pkgs that are,
if API, ABI changes, are always released together (that's the
only promise from upstream!!).
>
> Also, you have a .la file in it. So the -dev package will need
> to make sure that all other .la files referenced in it get
> installed too by adding the correct Depends.
They only 'benefit' from lib and -dev split is more pkg# bloat,
with every minor release, more useless (IMHO) maintainer
work and last but not least ftp-master is always pestered because
of a NEW and obsolete lib pkg. And last but not least that
everyone dare to use the lib and dev pkgs will be disappointed
due to the continous API breakage.
If I miss a/the point, please let me know. Otherwise I would
like reopen/downgrade/won't fix this bug and revert the split until
upstream decides to maintain libdigikam as a real shared
library with a proper maintained API and version handling.
> PS: I recommend you upgrade the libtool version in the package to
> the version in debian. The one you're using is rather old.
AFAIU KDEs build system uses it own forked version of libtool.
No good idea to poke around there. Any change needed here
should be done upstream because almost every KDE appl release
uses the build code used in KDE svn.
Achim
>
>
> Kurt
--
To me vi is Zen. To use vi is to practice zen. Every command is
a koan. Profound to the user, unintelligible to the uninitiated.
You discover truth everytime you use it.
-- [EMAIL PROTECTED]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
