On Mon, Oct 22, 2018 at 09:56:04AM +1000, Allan McRae wrote: > On 22/10/18 8:57 am, Eli Schwartz wrote: > >> Also, most projects ship prebuilt man pages. I think some GNU ones > >> commit the built page to the tree, so that could be an option. > > > Both those things are also true about the configure and Makefile.in files... > > That is another good reason not to use git archive to create release > tarballs. > > A
Consider that the reason we need 'make dist' and can't just use 'git archive' is because autotools *requires* extra tooling around just to generate the build system. This is no longer needed with meson. Pre-generating the manpages means that our substitutions are invalidated. For example, someone building from the tarball with --prefix=/some/where/else or no --prefix at all will have a pacman.conf(5) that still claims the right path is /etc/pacman.conf I understand your point about python2 vs python3, but I think that's something we can work out based on a python3-based asciidoc in existance. What problems here would you like to see solved for the inclusion of meson? That will help me focus my time spent on this. dR
