Re: Documentation Policy
From: "Scott K. Ellis" <email@example.com>
> I have no problem when HTML is the provided upstream documentation source,
> and don't want to cripple my ability to read that. However, when the
> upstream source is something else, such as info/texinfo, I don't want HTML
> as well.
Well, you're going to need a script to implement that policy. Probably
the best way to handle this is to provide a way to tell the package system
that you have deliberately removed a file, and that this file should not
be replaced. I wouldn't expect this in version 1.0 .
Bruce Perens K6BP firstname.lastname@example.org 510-215-3502
Finger email@example.com for PGP public key.
PGP fingerprint = 88 6A 15 D0 65 D4 A3 A6 1F 89 6A 76 95 24 87 B3
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
Trouble? e-mail to firstname.lastname@example.org .