Re: Policy for /usr/doc/<pkg-name>-doc
Hi
>>"Avery" == Avery Pennarun <apenwarr@worldvisions.ca> writes:
Avery> On Fri, Nov 06, 1998 at 05:02:34PM +0000, Manoj Srivastava wrote:
>> What about a mixed solution: the documentation is always in
>> /usr/doc/<package>, but /usr/doc/<package>-doc exists and contains
>> the copyright, the changelog, and other adminstrivia required by
>> policy.
Avery> Come to think of it, if the binary and -doc copyright files
Avery> are different, and the documentation ends up in
Avery> /usr/doc/package (not package-doc), then how do we know which
Avery> copyright applies to which files?
In that case, the documentation files remain in
/usr/doc/<package>-doc, with a possible README.docs file added to
/usr/doc/<package> (with explicit copyright information for the file,
if needed ;-).
I think I agree with Raul. The general solution seems to be
documentation, not rearrangement, and letting the package maintainers
choose which way to go (as long as they document it).
manoj
--
BYTE editors are people who separate the wheat from the chaff, and
then carefully print the chaff.
Manoj Srivastava <srivasta@acm.org> <http://www.datasync.com/%7Esrivasta/>
Key C7261095 fingerprint = CB D9 F4 12 68 07 E4 05 CC 2D 27 12 1D F5 E8 6E
Reply to: