On Fri, Dec 09, 2016 at 11:48:46PM -0800, Steve Beattie wrote:
> On Wed, Nov 30, 2016 at 03:31:59PM -0800, Steve Beattie wrote:
> > An additional step that I didn't do here would be to
> > remove the pdf from the default build path, to ensure that it doesn't
> > get triggered to build.
>
> Here's
On Wed, Nov 30, 2016 at 03:31:59PM -0800, Steve Beattie wrote:
> Attached are two alternative patches for avoiding the problem of
> building the parser's techdoc during the build, which introduces
> the latex stack as build dependencies for downstreams, and is also
> a source of unrepeatability in
On 12/09/2016 11:48 PM, Steve Beattie wrote:
> On Wed, Nov 30, 2016 at 03:31:59PM -0800, Steve Beattie wrote:
>> An additional step that I didn't do here would be to
>> remove the pdf from the default build path, to ensure that it doesn't
>> get triggered to build.
>
> Here's the patch to do that
On Thu, Dec 01, 2016 at 10:31:18PM +0100, Christian Boltz wrote:
> I vote for keeping techdoc and creating the PDF at tarball creation, so
>
> apparmor-build_docs_w_tarball.patch
> Acked-by: Christian Boltz
>
> I didn't test your patch, so please create a test tarball to make sure
> the PDF rea
On Wed, Nov 30, 2016 at 03:31:59PM -0800, Steve Beattie wrote:
> An additional step that I didn't do here would be to
> remove the pdf from the default build path, to ensure that it doesn't
> get triggered to build.
Here's the patch to do that as well, by creating an extra_docs target
and using it
Hello,
Am Mittwoch, 30. November 2016, 15:52:47 CET schrieb Seth Arnold:
> On Wed, Nov 30, 2016 at 03:31:59PM -0800, Steve Beattie wrote:
> > The alternative patch removes the techdoc and the steps to build it
> > entirely. It has not been updated meaningfully since 2007, and no
> > one
> > seems
On Wed, Nov 30, 2016 at 03:31:59PM -0800, Steve Beattie wrote:
> The alternative patch removes the techdoc and the steps to build it
> entirely. It has not been updated meaningfully since 2007, and no one
> seems to have time to take on bringing it up to date. Furthermore,
> John has created his ow