On Wed, Aug 15, 2018 at 12:44:01AM +1000, Duncan Roe wrote:
> On Tue, Aug 14, 2018 at 02:51:45PM +0200, Pablo Neira Ayuso wrote:
> > This adds unnecessary complexity to our build infrastructure. People can
> > just manually generate them in PDF in case they need too. So let's keep
> > it simple and remove this.
> >
> > Signed-off-by: Pablo Neira Ayuso <pablo@xxxxxxxxxxxxx>
> [...]
>
> I thought they looked rather nice. They scrolled more easily than a man page and
> didn't use up an xterm. And you *did* have to specify at configure time that you
> wanted them, which I suspect most distros won't do.
>
> Please reconsider,
As an alternative, would you be OK if we keep in the tree a
build-pdf.sh script that calls asciidoc to generate the PDF? So we get
this away from the build infrastructure but still you have an easy
way to quickly build the documentation in PDF file format? If you're
fine with this approach, send me a patch with that script and I'll
apply it. We can probably even make it generic so one could generate
it in HTML too, eg.
./build-docs.sh pdf
or
./build-docs.sh html
This is the only software in netfilter.org that comes with built-in
infra to generate a PDF file, while I understand a more friendly
format is useful to scroll up and down, I see no benefit in keeping
infrastructure to autogenerate this when most distros will simply skip
this.
Let me know, thanks.
