From: tmz at pobox.com (Todd Zullinger)
Subject: [RFC PATCH] Makefile: work around parallel make issues in docs
Date: Sat, 16 Jun 2018 13:52:14 -0400 [thread overview]
Message-ID: <20180616175213.GG11827@zaya.teonanacatl.net> (raw)
In-Reply-To: <20180616171853.GJ1922@john.keeping.me.uk>
Hi,
John Keeping wrote:
> On Sat, Jun 16, 2018 at 12:32:06PM -0400, Todd Zullinger wrote:
>> We might also want to drop 'doc-pdf' from the default 'doc'
>> target. The alternative is driving the asciidoc pipeline
>> for the pdf generation too. That looks a little more
>> involved than doing it for html, but perhaps it's not as bad
>> as I think.
>
> I think we can definitely drop doc-pdf from the default output.
>
> I'm half tempted to say we should just delete the PDF output completely
> and see if anyone complains, unless you know of anyone using this?
We don't generate the pdf docs for the Fedora/EPEL cgit
builds and no one has yet filed a bug asking for it. Poking
around, none of Arch, Debian, Gentoo, and Ubuntu build the
pdf docs (in fact, they don't include the html target
either).
Maybe that's a good sign that the pdf target wouldn't be
missed by many people.
> Otherwise, the dependency on $(DOC_MAN5) seems reasonable
> to me, probably accompanied with a comment explaining the
> clash in a2x's intermediate files.
Cool. I'll wait a bit and see if anyone chimes in with
support for keeping the pdf target. If not, dropping it is
the easier option.
Thanks,
--
Todd
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
I dropped acid on a Saturday night Just to see what the fuss was
about. Now there goes the neighborhood.
prev parent reply other threads:[~2018-06-16 17:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-16 5:38 tmz
2018-06-16 6:55 ` thomas.moschny
2018-06-16 16:40 ` tmz
2018-06-16 12:20 ` john
2018-06-16 12:50 ` Jason
2018-06-16 16:32 ` tmz
2018-06-16 17:18 ` john
2018-06-16 17:52 ` tmz [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180616175213.GG11827@zaya.teonanacatl.net \
--to=cgit@lists.zx2c4.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).