On Sun, Feb 25, 2001 at 01:04:18PM +0000, Julian Gilbey wrote: > On Sun, Feb 25, 2001 at 05:56:16AM -0600, Sam TH wrote: > > > >From current policy: > > > > > > When specifying the set of build-time dependencies, one should list > > > only those packages explicitly required by the build. It is not > > > necessary to list packages which are required merely because some > > > other package in the list of build-time dependencies depends on them. > > > The reason is that dependencies change, and you should list only those > > > _you_ need. What others need is their business. > > > > > > Hopefully this will answer your question. > > > > Well, sort of. For the packe in question, it does. But say there was > > a package that depended on both GLib and GNOME (say, by including > > gnome.h and glib.h). If, at some later point, GNOME no longer > > depended on GLib, then just having Build-Depends: libgnome-dev would > > no longer be correct. But currently it is. What should one do in > > this situation? > > So if you need both gnome.h and glib.h, then you must Build-Depends: > libgnome-dev, glib-dev, because these packages are both *explicitly* > required by the build. Ok, that's what I expected. It just makes it harder to do the chroot-and-see-what-packages-you-need thing. Oh well. sam th sam@uchicago.edu http://www.abisource.com/~sam/ GnuPG Key: http://www.abisource.com/~sam/key
Attachment:
pgp9EYFOzMpfM.pgp
Description: PGP signature