linux-kernel - Re: [PATCH RFC 0/4] Fix PDF build errors

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20161102214715.mgpjctxzif3rb6z4@wfg-t540p.sh.intel.com>
Date:   Thu, 3 Nov 2016 05:47:15 +0800
From:   Fengguang Wu <fengguang.wu@...el.com>
To:     Jani Nikula <jani.nikula@...ux.intel.com>
Cc:     Mauro Carvalho Chehab <mchehab@...radead.org>,
        Mauro Carvalho Chehab <mchehab@....samsung.com>,
        Linux Doc Mailing List <linux-doc@...r.kernel.org>,
        Jim Davis <jim.epost@...il.com>,
        Jonathan Corbet <corbet@....net>,
        linux-kernel <linux-kernel@...r.kernel.org>, kbuild-all@...org,
        Philip Li <philip.li@...el.com>
Subject: Re: [PATCH RFC 0/4] Fix PDF build errors

On Wed, Nov 02, 2016 at 03:27:50PM +0200, Jani Nikula wrote:
>On Wed, 02 Nov 2016, Mauro Carvalho Chehab <mchehab@...radead.org> wrote:
>> Em Wed, 02 Nov 2016 13:14:47 +0200
>> Jani Nikula <jani.nikula@...ux.intel.com> escreveu:
>>
>>> On Wed, 02 Nov 2016, Mauro Carvalho Chehab <mchehab@....samsung.com> wrote:
>>> > This series address a series of errors during PDF generation from
>>> > media documentation.
>>> >
>>> > Please notice that patch 2 carries on a PDF conversion from a PNG
>>> > image, because Sphinx is not smart enough to do the convertion.
>>> >
>>> > This is a temporary solution (That's why I'm marking this series
>>> > as RFC).
>>>
>>> This seems to work on top of docs-next.
>>
>> Yes.
>>
>>> ...but it'll break again if we include the missing admin-guide in the
>>> build. :(
>>
>> LaTeX/PDF output is ugly... for each new stuff, we need to re-validate its
>> output :-(
>
>Once we have this working, I think the only way to keep it working is to
>have continuous testing of the pdf build. That won't keep the output
>pretty, but it'll help ensure passing build.
>
>Perhaps 0day could eventually start running 'make DOCBOOKS="" pdfdocs'
>after the htmldocs target? Cc: Fengguang and kbuild-all.

OK. We'll add the 'pdfdocs' test right after 'htmldocs'.
Thank you for the tip.

Regards,
Fengguang