Re: master c86995d07e9: Enable code block evaluation when generating .org manuals

[Stefan Kangas <stefankangas@gmail.com>]

Ihor Radchenko <yantar92@posteo.net> writes:

> Stefan Kangas <stefankangas@gmail.com> writes:
>
>> Kyle Meyer <kyle@kyleam.com> writes:
>>
>>> As mentioned by Ihor (+cc) in bug#71394, this change is needed before
>>> syncing the latest Org release to the Emacs tree due to Org's 715148131
>>> (org-manual: Automatically generate export option list, 2023-07-31).
>>
>> Does it really need to generated automatically on every build, or can it
>> be handled in some other way?  For example, we pre-generate our loaddefs
>> files and commit the result.
>
> Preferably, every build, I think.
>
> What we do in Org mode manual is examining an Elisp variable and build a
> table summarizing its values. If that variable changes in the code, the
> manual should reflect this change.

Right, but the same is true for our loaddefs files (you want them
up-to-date, or you get warnings, etc.), and even for them it's been
enough to have a cronjob regenerate and commit them once per month.

So I think my question still stands.