Re: policy summary (new packages without man pages)
Richard Braakman writes:
> Indeed. Consider, though, that writing a small manpage that points
> at existing documentation is not onerous. It is about as hard as
> figuring out how to create a menu entry. I think it's part of the
> packaging process.
It's tricky to write a decent manpage if you know no nroff.
> If a package doesn't have *any* documentation, then there's not much
> point in packaging it -- only people who have source code will be
> able to use it.
Hence a) the previous suggestion of having standard manpages pointing
to info /usr/share/doc/ or whatever.
Besides foo --help is often all you need to get at least basic
functionality from a package. Or, in the case of beta software, the
author says "Developers should be able to manage with the commented
header file. I'll write more documentation at a later stage", I'm
inclined to agree with upstream, and provide the header file in the
appropriate place, with a comment in Readme.Debian.
Matthew
--
"At least you know where you are with Microsoft."
"True. I just wish I'd brought a paddle."
http://www.debian.org
Reply to: