On Tue, Nov 23, 1999 at 07:31:01PM +0100, Goswin Brederlow wrote: > Package: debian-policy > Version: 3.1.1.0 > Severity: wishlist > > Policy says that any binary must come with a manpage. I would like to have > the same for packages. > > I just looked for a parser generator that outputs C++ code and found pccts. > After installation I tried "man pccts", but that failed. > /usr/doc/pccts doesn't contain examples, so how do I use the thing? > > pccts in fact contains several binaries, but non is called pccts. The main > binary is called antlr and has a good manpage. > > My suggestion is now, that "man pccts" should eigther point to the main > binarys manpage or show a page that gives a oneline description of the > binaries of the package or one that has just relevant "see also: xxx" entries.
How about someone write a script that pulls all of the packages and if there isn't a man page matching the package name, create one using the package's description as the content. Call it "update-packageman" or something. However, I don't think this should be policy, just a simple tool. -- -----------=======-=-======-=========-----------=====------------=-=------ / Ben Collins -- ...on that fantastic voyage... -- Debian GNU/Linux \ ` [EMAIL PROTECTED] - [EMAIL PROTECTED] - [EMAIL PROTECTED] ' `---=========------=======-------------=-=-----=-===-======-------=--=---'
