help-shishi
[Top][All Lists]
Advanced

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

Re: debian build of 0.35


From: Simon Josefsson
Subject: Re: debian build of 0.35
Date: Thu, 07 Feb 2008 15:21:57 +0100
User-agent: Gnus/5.110007 (No Gnus v0.7) Emacs/22.1 (gnu/linux)

Another issue came up when packaging 0.35, lintian complained:

W: shishi-dbg: dbg-package-missing-depends shishi
N:
N:   This package has a name of the form of "X-dbg", indicating it contains
N:   detached debugging symbols for the package X. If so, it should depend
N:   on the corresponding package, generally with (= ${binary:Version})
N:   since the debugging symbols are only useful with the binaries created
N:   by the same build.
N:

That was likely because 'shishi-dbg' only depend on libshishi (=
${binary:Version}), not the other packages for which it also contains
debugging information.

I did install the following fix:

-Depends: libshishi0 (= ${binary:Version})
+Depends: libshishi0 (= ${binary:Version}),
+ libshisa0 (= ${binary:Version}),
+ shishi (= ${binary:Version}),
+ shisa (= ${binary:Version}),
+ shishi-kdc (= ${binary:Version}),
+ libpam-shishi (= ${binary:Version})

But then I realized this probably isn't a good idea... a user should be
able to install 'shishi-dbg' without having to pull in shishi-kdc etc.

How can this be resolved?  Should there be one -dbg package for each
binary package?  I.e., libshishi0-dbg, libshisa0-dbg, shishi-dbg,
shisa-dbg, shishi-kdc-dbg, libpam-shishi-dbg?  That seems quite
wasteful, but I'm not sure how to avoid it.

/Simon




reply via email to

[Prev in Thread] Current Thread [Next in Thread]