> This is quite unrelated, but I still think that we should split current > DATADIR/texinfo content in two, add DATADIR/texi2any for Perl modules, > js files, Perl external modules, ext and init files shipped with > texi2any. That way we can use DATADIR/texinfo only for files that > could, at least theoretically, be shared across implementations. That > would be htmlxref.cnf files, maybe the Texinfo DTD, could also be some > icon images for directions, CSS files examples, and, in a distant > future, even init files if they can be shared among implementations.
I saw you made this change. Now there are only 3 files installed under DATADIR/texinfo: texinfo/texindex.awk texinfo/htmlxref.cnf texinfo/texinfo.dtd texinfo.dtd is coupled to the exact version of texi2any that is installed although texi2any does not actually access this file. (It's also a pointless file as nobody uses --xml output for anything and I'd be quite happy to have this output format removed in the future. So we shouldn't add subdirectories to install files like DATADIR/texinfo/7.1/texinfo.dtd.) I don't know if htmlxref.cnf should be installed under DATADIR/texinfo or DATADIR/texi2any. texi2any needs to access it and I don't know if we are encouraging people to edit the installed version of htmlxref.cnf. It is not like DATADIR/info/dir which we don't install and which people are encouraged to edit. I thought that it might be a good idea to use DATADIR/texi2any for all texi2any files in case texi2any becomes its own project in the future, separate from other parts of Texinfo. It could be something to consider for the interests of long-term maintainabilty although I am not proposing that it happens at present. texindex.awk is used by texindex installed undir BINDIR. So I doubt we can easily make DATADIR/texinfo a completely version-independent directory (along the lines of DATADIR/info). However, it could be possible to have subdirectories of DATADIR/texinfo used for this purpose (DATADIR/texinfo/init and so on).
