On 09:14 02 Aug 2002, Chris Palmer <[EMAIL PROTECTED]> wrote:
| Vincent Lefevre writes:
| > > The installed manual should be preprocessed during the build to have
| > > the correct defaults.
| > But how can it have the correct defaults since there is only one
| > manual for several binaries?
Only on sloppy installs.
| What several binaries? My system has only one /usr/local/bin/mutt.
|
| Cameron means that, at compile/configure time, the source of the man
| page would be modified programmatically to agree with the ./configure
| options.
| (Which is, btw, the best solution.)
Or that mutt has a -dump-defaults option, which is used post build,
during install, to mangle the muttrc man page. Hell, with the embedded
help text in the binary, much of the manual entry could be _generated_
from the binary!
On my systems I frequently have several mutts installed.
Each has its own manual page because each has its own install tree.
The /usr/local/bin/mutt is a symlink to the appropriate mutt binary
in its respective tree, and so is the manual entry.
Users wanting the nondefault mutt put
/opt/mutt-version/bin
in their PATH and
/opt/mutt-version/man
in their MANPATH. And lo, they get matching binaries and manuals.
This is not hard. It's almost trivially easy.
Ask yourselves: _why_ do you have multiple mutt binaries? Because they
have _different_ behaviours! And so the should have different manual
entries.
Cheers,
--
Cameron Simpson, DoD#743 [EMAIL PROTECTED] http://www.zip.com.au/~cs/
The betas never stop at Microsoft. - news.com
