[Swan-dev] always generating the man page

Andrew Cagney andrew.cagney at gmail.com
Tue May 12 03:18:41 EEST 2015

On 11 May 2015 at 13:49, D. Hugh Redelmeier <hugh at mimosa.com> wrote:

> | From: Paul Wouters <paul at nohats.ca>
> | But since we don't export a shared library, we don't have a devel
> | package that would include the headers and developer man pages....
> Right.  Simplest solution that kind of works:  build those manpages,
> but don't install them.  Why build them?  Because they are hard to
> read otherwise.  This wasn't true in Henry's day (because we wrote
> directly in *roff).

FYI, I've pushed the following:

- any existing library make file rules that build/install man page have
been removed; i.e., library man pages no longer get installed

- some of library manpages that appear to have been generated from .xml
source have also been removed; the process is fragile so I'm being slightly

If a library man page needs to be build, then perhaps "make foo.8" will
work (I'm claiming plausible deny-ability has testing would likely result
in more work ... :-)

I also have to wonder if the knowledge contained in some of these man pages
should be folded back into the source; and, to take this off topic, if even
the libraries that only programs/pluto/ uses should be deemed failed
experiments and moved back to programs/pluto :-)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.libreswan.org/pipermail/swan-dev/attachments/20150511/60260bd7/attachment.html>

More information about the Swan-dev mailing list