Hi Colin. Colin Watson wrote: >>Should I have doxygen generate manpages and include them in the -doc >>package? [..] > I think it's a good idea, although I'm biased. :) That's fair enough. The point that made me think though, is the possibility that the benefit of man pages declines sharply with the focus of the library (i.e. I would conjecture that with highly specialized libraries, where one usually investigates the design of the library before starting to use it, most often, the documentation will be consulted non-manpage format (e.g. html), while for "omnipresent" libraries like libc, where one usually only needs to look up a couple of functions as a reminder, the manpages are extremely useful).
As an additional hinderence, the library has a c++ interface, from which the doxygen creates thousands of one-liner .so man-pages. (One for each member.) With this strategy, it is painfully clear, that the man namespace is utterly cluttered with junk. (There's nothing objectionable about a SomeClass::write method, but a write.3 manpage for this?) Cheers Thomas
msg08605/pgp00000.pgp
Description: PGP signature