Bug#347581: debian-policy: Explicitly permit *-headers binary package created from library source package
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Chris Waters wrote:
> On Wed, Jan 11, 2006 at 11:19:05AM -0500, Kevin B. McCarty wrote:
>>Without this or a similar text, it is not clear to me that source
>>packages creating <library>-headers binary packages are in compliance
>>with Policy, which currently says "The development files associated to a
>>shared library need to be placed in a package called
>>librarynamesoversion-dev, or if you prefer only to support one
>>development version at a time, libraryname-dev."
>
> I would rather see that last sentence modified slightly to allow a
> little more flexibility. Perhaps changing "placed in" to "placed in
> or installed by". Or something along those lines.
Hmm, how about this? (I can't quite see how to keep it to a single
sentence of reasonable length.)
"If there are development files associated to a shared library, the
source package needs to generate a binary development package called
librarynamesoversion-dev, or if you prefer only to support one
development version at a time, libraryname-dev. Installing the
development package must result in installation of all the development
files."
This change would leave the door open for development files to be split
up into separate packages as needed, as long as lib<whatever>-dev
depends upon all of them, either directly or indirectly.
- --
Kevin B. McCarty <kmccarty@princeton.edu> Physics Department
WWW: http://www.princeton.edu/~kmccarty/ Princeton University
GPG: public key ID 4F83C751 Princeton, NJ 08544
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFDxqxffYxAIk+Dx1ERAq7BAJ45NWQTVTONEpjioHS9MuQ+HfVzuQCfekjQ
+0cx8IB0WddGCk+pGVsKTqg=
=hcZW
-----END PGP SIGNATURE-----
Reply to: