Re: man2html

> Just using man2html from the man package
> fixes things sufficiently for my purposes.

Yes it does - in MacPorts, which now uses this particular man2html.
There are many other man2html's out there (all as shit as this one),
so it's entirely possible this same thing is broken on other systems.

> A number of projects have a configure switch that enables/disables
> developer documentation.

A manpage for the binaries is not developer documentation,
it's user documentation. A description of the API is developer
documentation, adn I  get it rght, that's currently built
with Doxygen, not related the the man2html problem (right?).

> Within MacPorts, we often have an install-time option to then include or exclude those docs (a “variant” in MacPorts-parlance).  Personally, I would always want the regular man pages included in the package.

Of course.

> Would it be a big project to make all the developer docs
> (including the html versions of the man pages) optional?

I believe it would be beneficial to have a default variant
that does not install the API docs and the html manual
(and whuch does not need doxygen and man and perhaps other stuff),
and a 'doc' variant (is there a prefferred name for such variants?)
taht would also install the API docs and the html manual.

(But that's a MacPorts question of course,
not relaed to LIRC itself).

	Jan


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot