On Sun, Oct 15, 2006 at 12:04:20PM +0200, Bill Allombert wrote: > On Sun, Oct 15, 2006 at 10:44:10AM +0100, Neil McGovern wrote: > > > > + <sect id="embeddedfiles"> > > > > + <heading>Embedding code provided in other packages</heading> > > > > + <p> > > > > + A package should not embed or include code from other > > > > + packages. Instead, the package should be modified to reference the > > > > + required files provided by the other package, and a Depends > > > > + relationship declared.</p> > > > > + </sect> > > > > </chapt> > > > > > > This does not address my concern. Every compiled C programs embed code > > > from the C library headers file but should not Depend on libc6-dev. > > > > However, every C program doesn't ship with it's own version of the C > > library header files, which is what we're trying to avoid. > > In that case, I suggest you change package by source package and Depends > by Build-Depends. Or am I missing something ? > Well, this section is an amendment to the source package section. Essentially, there's been a large number of packages recently that embed code from other packages in their own. Included in this is static complilation, but this seems to be covered by another bit of policy. We want to avoid packages shipping their own versions of libraries, as then if a security problem or major bug is discovered in that library, we have lots of packages to update, and there's no garuntee we'll even know which packages it affects. Cheers, Neil -- * stockholm calls netapp * stockholm calls someone else <Ganneff> you are typing random numbers on your phone? <stockholm> yes. my newest attempt to close our budget hole
Attachment:
signature.asc
Description: Digital signature