Josselin Mouette <j...@debian.org> writes: > Yes, I overall agree with your arguments. However having it in the > policy means we get bug reports about manual pages and have to deal > with them, while they are not the primary source of documentation for > command-line options.
If manpages were useful only for documenting command-line options, this would be a valid point. As has been pointed out, though, manpages for programs are useful for much more than that. > In my opinion, we’d be better off with no manual page than with one > that is not maintained correctly. However the current policy > encourages shipping a buggy manual page over not shipping it at all. This is a problem, yes, I hadn't thought about it that way. Thank you. So is it feasible to instead come up with a phrasing that encourages full up-to-date manpages, but doesn't encourage keeping out-of-date manpages? -- \ “Software patents provide one more means of controlling access | `\ to information. They are the tool of choice for the internet | _o__) highwayman.” —Anthony Taylor | Ben Finney
pgpIZtgxh36B3.pgp
Description: PGP signature
