Copyright file in multipart packages?
-----BEGIN PGP SIGNED MESSAGE-----
Policy question:
When handling a binary package split into components, how does one
deal with the /usr/doc structure and the copyright file (which would be
identical between components)? The structure I'm dealing with right now
is this:
iraf_...-1.deb
iraf-common_
iraf-ibin_
iraf-noaobin_
where the first depends upon the next three. The way I see it,
for it to really be findable, the primary doc directory should be
/usr/doc/iraf, and there should be a physical file "copyright" in that
directory. It seems somewhat odd to me to create
/usr/doc/iraf-common, /usr/doc/iraf-ibin and /usr/doc/iraf-noaobin
just to put a single file "copyright" which is duplicated
byte-for-byte in /usr/doc/iraf. Policy 5.5.6 mentions that /usr/doc/x
can be a symlink to /usr/doc/y if x depends on y, but here that
doesn't work, since I'd want a symlink from iraf-common to iraf, and
iraf would depend on iraf-common, not the other way around.
If in fact that kind if symlinking is what is appropriate,
however, how then does one handle the copyright file itself? The jdk
non-free packages handled it by changing the name of copyright to
copyright, copyright-shared, copyright-static, etc. depending upon the
package segment, but lintian gives that approach a thumbs-down, and
from the perspective of someone wanting to be able to automatically
display the copyright out of a .deb, that doesn't work very well
either. At the same time, if I symlink, I can't give them all the
same name, as they'll conflict with each other. And it doesn't seem
appropriate in any case to symlink and then have a package with no
actual copyright text in it.
Comments?
=============================================================================
Zed Pobre <zcp@po.cwru.edu> | PGP key on servers, fingerprint on finger
=============================================================================
-----BEGIN PGP SIGNATURE-----
Version: 5.0
Charset: noconv
iQEVAwUBNO3CftwPDK/EqFJbAQHkNwf/dvZQXRVQ3aFJWoVriZRVLN3h7vAoes1f
JK+/fU+jAtEAzlOstcUwMkHhyX4Q1S4h1Ecp43YHl4P3HYKgEmMQtxb7XOPNJols
Djtg0YDMfan+kiRIeALGRr4ia5xecXNis5VKt1G6gxKKnAxQb4Xth5Dtbf6OGNUP
YbtTCLDJyQC8HsTfJ715hWewxY1JbE1cTSWloW8jToVBziNNjD2/rNozxtJIfS4y
bOX+BYEUrO7w5i7ZoFZiBsM175F9g0elNfyUsaPXMEE8vnQfPXwzwU9wnbPlY1q7
5vgubMxD2qVs8DRn2GNnNMJ8yggtuVIed2zkmwBtwLo9SUZAJhQocQ==
=jslA
-----END PGP SIGNATURE-----
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
debian-devel-request@lists.debian.org .
Trouble? e-mail to templin@bucknell.edu .
Reply to: