Re: HTML in addition to GNU Info? (was: ... instead ...)
- To: firstname.lastname@example.org
- Subject: Re: HTML in addition to GNU Info? (was: ... instead ...)
- From: email@example.com (Karl M. Hegbloom)
- Date: 09 Jul 1999 00:28:54 -0700
- Message-id: <[🔎] firstname.lastname@example.org>
- In-reply-to: Norbert Nemec's message of "Sun, 20 Jun 1999 18:42:21 +0200"
- References: <19990613001538.A2136@DeepThought.> <19990613005455.A306@flora.ruhr-uni-bochum.de> <email@example.com> <19990619234718.F12720@localhost> <19990620184221.A737@DeepThought.>
>>>>> "Norbert" == Norbert Nemec <firstname.lastname@example.org> writes:
Norbert> - include texi files in the packages and let a mechanism
Norbert> create the files the sysad wants on the system.
How about include a target in debian/rules that builds .ps, .dvi, or
.pdf versions of .texi documentation, but don't ship those with the
binary.deb. Ship the .info by default, .html in a separate -doc
package (many of us will not install HTML; it is CRUFT when `info' is
available.), and leave the .texi in the source package, with a target
that makes ungreppables for those who wish to print or pdf and don't
know the commands or don't know where to find the fine manual to the
Generally, a program that is documented with texinfo will have
targets in Makefile for .ps and .dvi, so a debian/rules standard
target would likely be fairly trivial to create.
I think more of us ought to learn texinfo and use it for new
manuals. `info undocumented' ;-)
The people who created `tex', `texinfo', and `info' are very wise.