A number of responses to my question seem to be confusing Debian Policy 4.2 which refers to "Build-depends:" that is packages necessary to build the package and the Debian Library Packaging guide section 6.2 which refers to the "Depends:" dependancies of the -dev packages that is the packages that the -dev package needs to work. A person installing a -dev package is not necessarily building packages and does not necessarily have build-essential installed. The text of 6.2 explicitly refers to libc-dev which everyone knows is in build essential. Please reconsider your answers in that light. Thank You. On Monday, August 22, 2011 04:54:20 AM Christoph Egger wrote: > Hi! > > Paul Elliott <pelliott@blackpatchpanel.com> writes: > > I quote from Debian Library Packaging guide > > > >> 2. -DEV package dependencies > >> > >> The -DEV package would usually declare Depends: relationship on all -DEV > >> packages for libraries that the library package directly depends upon, > >> with the specific SONAME version that the library package is linked > >> against. This includes libc-dev. [5] > > > > Does this mean that if my library has an include reference > > #include <stdio.h> > > in one of its .c or .h files, then my -dev package must have a depends > > line > > > like this in its debian/control file: > You need that for packages ∉ build-essential that any of your public > headers includes. No reason to do that for some .c files. I've basically > never ever seen a -dev package depending on libc-dev. > > Regards > > Christoph -- Paul Elliott 1(512)837-1096 pelliott@BlackPatchPanel.com PMB 181, 11900 Metric Blvd Suite J http://www.free.blackpatchpanel.com/pme/ Austin TX 78758-3117
Attachment:
signature.asc
Description: This is a digitally signed message part.