On Tue, Nov 9, 2010 at 4:08 PM, Mats Erik Andersson <mats.anders...@gisladisker.se> wrote: > Dear Mentors, > > I am about to package a graphical software, and I must properly > design a "Build-Depends" stanza in the control file. My concern > right now is whether I am allowed to prune the enumeration so > hard that the primary dependencies pull in all secondary and > tertiary ones, thus circumventing a natural desire to also > mention build dependencies that exist but are "shadowed". > > The particular case that comes to my mind is "libgtk2.0-dev", > which depends on "libpng12-dev" and "pkg-config", which I otherwise > would have mentioned, out of informational purpose, as build > dependencies of the package. Clearly, I would not have mentioned > all secondary dependencies, only those that do directly influence > the package at build time.
If libgtk2.0-dev was changed so that it no longer depended on libpng12-dev or pkg-config, would your package still depend on them? If so, they should be part of your dependency list. -- 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/aanlkti=w3hdhb_gw-2rlhhp-absmik3ebzv8vaa61...@mail.gmail.com
