Re: [PATCH 2/2] ci: use system asciidoctor

From: Jeff King <peff@peff.net>
Date: Sep 11, 2026, 20:42 UTC
Message-ID: <20260911204254.GB1622087@coredump.intra.peff.net>
In-Reply-To: <20260905152300.Zo2Zl39n@teonanacatl.net>

On Sat, Sep 05, 2026 at 11:23:00AM -0400, Todd Zullinger wrote:

> As none of the CI jobs are installing documentation against
> any RHEL-like targets, this doesn't matter much.  But if we
> were, we'd need to install the 'epel-release' package before
> installing asciidoctor, perhaps something like this:

Thanks, that's good to know, though I hope we'll never need to use it the information. :)

Show 5 quoted lines

> I'm happy to see more Asciidoctor support.  It seems to
> produce moderately better output than Asciidoc, in my
> experience.  Though I admit I haven't looked closely at
> Asciidoc after development picked back up a little to add
> Python 3 support and keep the project going.

Yeah, I think we were ready (mentally at least) to transition when it looked like asciidoc was unmaintained. The dual-tool system does occasionally introduce extra work, but I don't know if there would be downsides to dropping support for asciidoc now. Presumably the biggest risk would be losing support for some platforms, though in general it's not the end of the world to pull in pre-formatted pages on such systems.

I'll leave exploring that for another day.

-Peff