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 ?
>
> In the example above, the binary package does embed code from the C
> header file.
I think what we want is:
- Every library that other packages may want to link to should
have a -dev package, so others can build depend on it. This
basicly means everything that has a library in /usr/lib.
- Every source package should have build-dependencies for the
libraries it wants to use that is not part of the same source
package.
- If the upstream versions contains a library that already is in
Debian in a seperate source package, it should either:
- make sure it's linked against the external package, and not
using the internal version.
- Remove the internal version.
- Deprecate static linking
Kurt
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
