Re: Monitoring debian/shlibs.local files?
Cyril Brulebois k...@debian.org writes:
xine-lib:
=
libxine 1 libxine1-bin (= ${binary:Version})
this is totally done on purpose to avoid circular dependencies, see bug
#454267.
moreover we are considering introducing an shlibs.local file for ffmpeg
for tightening internal dependencies in the generated binary package
from the source.
both packages have the same motivation: Make dpkg-shlibdeps behave
differently for generated binary packages compared to packages linking
against the library. I acknowledge that this is rather rare and should
be used in general, but for these two cases, I find shlibs.local a
totally reasonable approach.
--
Gruesse/greetings,
Reinhard Tartler, KeyID 945348A4
--
To UNSUBSCRIBE, email to debian-qa-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Monitoring debian/shlibs.local files?
Loïc Minier wrote: On Mon, Dec 22, 2008, Adeodato Simó wrote: it is also with ideas like this that i regret that our policy process won't allow for a top-down flow of recommendations. imho this would be a nice use for it, once consensus was be reached that this is a good idea. The good thing is that lintian people are quite open to clever changes; this gives us immediately: - a mean to test a package - a mean to tell maintainers about it (if they run lintian) and hence put the actual work on their side - an up-to-date db of the affected packages (lintian.d.o) So, what exactly should be checked? and what's the status of this proposal? Cheers, -- Raphael Geissert - Debian Maintainer www.debian.org - get.debian.net -- To UNSUBSCRIBE, email to debian-qa-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Monitoring debian/shlibs.local files?
Raphael Geissert atomo64+deb...@gmail.com (28/01/2009): So, what exactly should be checked? and what's the status of this proposal? Dunno for others, but I for one am busy processing NMs and fixing RC bugs, I don't think any immediate action is needed at this point. (But moving on would be appropriate once lenny is out, AFAICT.) Mraw, KiBi. signature.asc Description: Digital signature
Re: Monitoring debian/shlibs.local files?
* Loïc Minier [Sun, 21 Dec 2008 20:31:16 +0100]: Just like we have descriptions for patches, we could require a description for shlibs.local, perhaps with a #xx bug in the text upon reading cyril's mail, i (also) thought it'd be nice if we could require a bug number in every shlibs.local file (but possibly nothing else!). the advantage of a bug over a description is that automated tools can detect stale shlib.local files (ie., when their bug has been closed for a while). it is also with ideas like this that i regret that our policy process won't allow for a top-down flow of recommendations. imho this would be a nice use for it, once consensus was be reached that this is a good idea. what's so wrong with that anyway? Cheers, -- Adeodato Simó dato at net.com.org.es Debian Developer adeodato at debian.org La música es de los que la quieren escuchar y de nadie más. -- Andrés Calamaro -- To UNSUBSCRIBE, email to debian-qa-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Monitoring debian/shlibs.local files?
On Mon, Dec 22, 2008, Adeodato Simó wrote: it is also with ideas like this that i regret that our policy process won't allow for a top-down flow of recommendations. imho this would be a nice use for it, once consensus was be reached that this is a good idea. The good thing is that lintian people are quite open to clever changes; this gives us immediately: - a mean to test a package - a mean to tell maintainers about it (if they run lintian) and hence put the actual work on their side - an up-to-date db of the affected packages (lintian.d.o) -- Loïc Minier -- To UNSUBSCRIBE, email to debian-qa-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Monitoring debian/shlibs.local files?
Hello, context: debian/shlibs.local can be used to work around broken shlibs files (Policy §8.6.5). Bugs are supposed to be filed, then fixed, and shlibs.local files should then disappear. I'm wondering whether it might be a good idea to track those in source packages, so as to make sure bugs got filed, and that those files go away. Having a fixed shlibs file would be profitable to all packages linking against this library, rather than having a single package getting its dependencies properly, through its shlibs.local file. Do you think it'd be worse the effort? (Didn't check the amount of such files yet, still performing my first AM steps.) Mraw, KiBi. signature.asc Description: Digital signature
Re: Monitoring debian/shlibs.local files?
On Sun, Dec 21, 2008, Cyril Brulebois wrote: I'm wondering whether it might be a good idea to track those in source packages, so as to make sure bugs got filed, and that those files go away. Having a fixed shlibs file would be profitable to all packages linking against this library, rather than having a single package getting its dependencies properly, through its shlibs.local file. I'm all for it; over time I came across a bunch of broken packages due to shlibs.local files, or simply with the risk of these files bitrotting and causing issues later. Just like we have descriptions for patches, we could require a description for shlibs.local, perhaps with a #xx bug in the text; when enough packages drop shlibs.local or implement the comment, we can add a lintian tag. I would expect not too many packages should keep it though; it's probably cruft in most cases. -- Loïc Minier -- To UNSUBSCRIBE, email to debian-qa-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Monitoring debian/shlibs.local files?
Loïc Minier l...@dooz.org (21/12/2008): I'm all for it; over time I came across a bunch of broken packages due to shlibs.local files, or simply with the risk of these files bitrotting and causing issues later. OK, since it doesn't look like useless, I'll look into it and report back in a moment. Mraw, KiBi. signature.asc Description: Digital signature
