--enable-doc waf config option removed

[James Browning]

On Sun, Feb 2, 2020 at 7:27 PM Eric S. Raymond via devel
<devel at ntpsec.org> wrote:
> Richard Laager via devel <devel at ntpsec.org>:
> > On 2/2/20 3:44 PM, Jason Azze via devel wrote:
> > > It looks like the --enable-doc waf configuration option was removed in the commit "Add support for other asciidoc processors". Was there any discussion about this change?
> >
> > Yes. See the mailing list archive and MR !1037.
>
> That MR conflated at least two changes that shouldb have been made
> separately. And I don't see any rationale for the questionable part,
> which is changing the configuration default.
>
> Thios is partly my fault.  U've been concentrating pretty hard on the
> GCC conversionm for months and havem't exercised the oversight I
> should have.  Well, that epic is over; I'm back.
>
> OK, I reached the relevant devs on #ntpsec.  Will pursue there.

Attached is a mostly untested patch that removes --disable-doc,
re-adds --enable-doc, and fails to build both mostly silently if
there is not a valid toolset available.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-Revert-policy-changes-from-Add-support-for-other-asc.patch
Type: text/x-patch
Size: 2037 bytes
Desc: not available
URL: <https://lists.ntpsec.org/pipermail/devel/attachments/20200202/d84f46cc/attachment.bin>