On Fri, Jan 26, 2024 at 09:08:16PM +0000, Gavin Smith wrote: > On Fri, Jan 26, 2024 at 03:57:24PM +0100, Patrice Dumas wrote: > > Hello, > > > > With an objective to improve gendoc.sh texinfo sources tarball > > generation code, I implemented, in the developpement version in git > > the possibility with texi2any to output the @include files included > > from a manual, without doing anything else. A bit like the -M option of > > cpp. For now this feature is set through the customization option > > SHOW_INCLUDE_FILE_PATHS. > > Is this so that gendoc.sh (a gnulib script, I believe),
Yes. > can get the list > of files so it can include them in a Texinfo source tarball? Yes. > How do > projects currently get the right files included, or do they not manage > to do this? They do not manage right now. > Have you made changes to this script to process the list > of included files? Yes, I have something preliminary that I attached. > > Is that interface to the feature ok? Would there be another way to > > specify included files that is common across diverse applications? > > Should we try to do something like -M? > > I don't like the idea of outputting Makefile rules but a list of included > files makes sense. I feel that a command-line argument (--trace-includes?) > would be better as the interface for this. Ok. (There will be a customization variable too, in that case). -- Pat
