[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20161102103618.2600485a@vela.lan>
Date: Wed, 2 Nov 2016 10:36:18 -0600
From: Mauro Carvalho Chehab <mchehab@...radead.org>
To: Jani Nikula <jani.nikula@...ux.intel.com>
Cc: 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>,
<fengguang.wu@...el.com>, kbuild-all@...org
Subject: Re: [PATCH RFC 0/4] Fix PDF build errors
Em Wed, 02 Nov 2016 15:27:50 +0200
Jani Nikula <jani.nikula@...ux.intel.com> escreveu:
> 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.
Yes.
> Perhaps 0day could eventually start running 'make DOCBOOKS="" pdfdocs'
> after the htmldocs target? Cc: Fengguang and kbuild-all.
Good idea! it will be really helpful if Fengguang could automate the
testing process once we fix it.
Regards,
Mauro
Powered by blists - more mailing lists