On Thu, Jan 03, 2013 at 09:41:15AM +0100, Reinhard Tartler wrote: > On Wed, Jan 2, 2013 at 10:26 PM, Wouter Verhelst <wou...@debian.org> wrote: > > On Wed, Jan 02, 2013 at 01:05:46PM +0100, Guillem Jover wrote: > >> - Private dependencies, as they leak to rdeps. When a library uses > >> another library privately this dependency gets linked in directly > >> in all other rdeps, when that library stop depending on that > >> private dependency, all rdeps need to be rebuilt. > > > > Strictly speaking, if you're only using static libraries this is not > > really true; once you've compiled something against a static library, > > the static library might change in whatever way it sees fit, the > > compiled binary will continue to work, with or without recompilation. > > Consider this from the application perspective: Say an application > links against a library libfoo.a. At some point, libfoo decides to > include compression support, and requires functionality from libz.
Ah, yes, but you're talking about /adding/ a dependency. Guillem's example was about removing one. There's a difference. -- Copyshops should do vouchers. So that next time some bureaucracy requires you to mail a form in triplicate, you can mail it just once, add a voucher, and save on postage. -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130104010625.ge2...@grep.be