On Fri, 18 Mar 2011, Paul Gevers wrote: > > Unfortunately this is wrong, at least for ELF binaries. Usually if you > > don't have all the dependencies that you expect, it's because they are > > optional and are disabled when they are not found during ./configure. > > Although I am just a simple DM, I still don't agree completely. Both my > upstreams call binaries (not libraries) in their programs (via a shell > or system call). As far as I can tell, that won't (and should not by the > name) be picked up by the ${shlibs:Depends} variable. Especially for the > shell call, I don't see an other way than providing it manually.
You're right on this one. But I think the question was about libraries from the start. Cheers, -- Raphaël Hertzog ◈ Debian Developer Follow my Debian News ▶ http://RaphaelHertzog.com (English) ▶ http://RaphaelHertzog.fr (Français) -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110319080222.ga31...@rivendell.home.ouaza.com