Am Freitag, dem 26.08.2022 um 17:33 +0300 schrieb Andrew Tropin: > > > > > > Cheers > > I went through a few popular packages and came up with conclusion > that it's hard to make good heuristic for automatical documentation > build: > > 1. I tried (find-files "." "\\.(texi|txi|texinfo)$") with consequent > for-each and it doesn't work in general case because it will build > files intended for inclusion, not standalone building. Fair enough, there's probably similar issues with org etc. That said, wouldn't the top-level info/org/whatever file share the package name? > 2. Adding automatic documentation build phase also means that almost > all emacs packages will be rebuild That's why I'm currently delaying native-comp until all other changes to emacs-build-system are done. > It seems that manual approach is more precise, less intrusive and > helps to get rid of many custom and non-uniform documentation build > phases. If you're going for a "manual" approach, I'd suggest instead making a curried ((build-documentation #:texinfo-files #:texinfo-regexp ...) #:outputs ...) so that the files can be written directly into the (add- after ...) syntax. Cheers