Re: Bug#392362: [PROPOSAL] Add should not embed code from other packages

[Bill Allombert <allomber@math.u-bordeaux.fr>]

On Wed, Oct 11, 2006 at 11:45:39AM +0100, Neil McGovern wrote:
> --- policy.sgml
> +++ policy.sgml
> @@ -2105,6 +2105,14 @@
>  	  the file to the list in <file>debian/files</file>.</p>
>        </sect>
>  
> +    <sect id="embededfiles">
> +      <heading>Embedding code provided in other packages</heading>
> +      <p>
> +      A package should not embed or include code from other
> +      packages. Instead, the package should me modified to link against the
> +      required files provided by the other package, and a Depends
> +      relationship declared.</p>
> +      </sect>
>      </chapt>

s/embededfiles/embeddedfiles/
s/me modified/be modified/

Actually almost all packages requiring some form of compilation do that. 
A C file that #include a header file from another package (e.g. the C library)
includes part of that package (the constant and inline function).
bison parsers embed a large part of bison source code.
Since we are a free software project, forking a program should be
possible without modifying all the files, it is actually the case
of a lot of packages (for example most window managers), and 
"be modified to link against the required files provided by the other
package" is very often impossible.

I am not sure we can realistically add a requirement higher than:

     A package should not link against copy of libraries packaged
     separately by Debian. 

Cheers,
-- 
Bill. <ballombe@debian.org>

Imagine a large red swirl here.