<div dir="ltr"><div><div><div><div><div><div><div><div><div>Several updates, and a question:<br><br></div>- I've added xmlto to the list of things installed in the test VMs<br><br></div>- I've started testing the below; be afraid<br><br></div>One annoying wart I've found is that some of the generated manpages get an ipsec_ prefix removed only to then be put back. During the build it does:<br></div> xmlto version.5.xml -> ipsec_version.5<br></div> mv ipsec_version.5 version.5<br></div><div>and then in the install it does:<br></div> install version.5 .../man5/ipsec_version.5<br></div>(technically the last is $(MANPROCPREFIX)version.5).<br><br>Does anyone know of a good reason to not simply dump this behaviour; and instead simply call man.xml files by their actual names?<br></div>For instance, version.5.xml would be renamed to ipsec_version.5.xml. If there really is a need to change ipsec_ to something else then that can be handled during install.<br><br></div>Andrew<br><div><div><div><div><div><div><div><div><div><br></div></div></div></div></div></div></div></div></div></div><div class="gmail_extra"><br><div class="gmail_quote">On 7 April 2015 at 11:23, Andrew Cagney <span dir="ltr"><<a href="mailto:andrew.cagney@gmail.com" target="_blank">andrew.cagney@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div><div><div><div><div>Having hit yet another directory where there wasn't a generated man page, I'm going to change the build system to something like:<br><br></div>make programs: only builds programs (i.e, no longer attempts to build man pages)<br></div>make man: builds man pages<br></div>make install-programs: only installs programs<br></div>make install-man: only installs man pages<br></div><div>make all: run programs and man<br><br></div><div>and perhaps:<br><br></div><div>make dist: runs "make man"<br></div><div><br></div>and remove any generated man pages. You'll notice that this lets us:<br><br></div><div>- continue to build/test/install on the VMs (they should have xmlto but don't)<br></div><div><br></div><div>Here's my spin on why:<br><br>Long long ago, before there were public repositories, everyone passed source tar-balls around (and before that shell archives, and before that, ...). To make things easier to build, the convention of including the generated documentation(1) and yacc(2) was adopted. As projects moved to public repositories, the convention stuck; well for a short while. It didn't take long before projects realized that it was far simpler and more robust(3) to only have the original source code in the repo. If it was felt that distributing generated files was helpful then the "make dist" target can handle that.<br><br></div><div>Andrew<br><br></div><div>(1) for instance bundling generated postscript/pdf files; perhaps man pages were bundled because groff was hard to build or didn't exist :-)<br></div><div>(2) try building bison without yacc or bison :-)<br></div><div>(3) one key issue is date stamps, you really can't trust a repo to preserve the modification date of files - this is why our current build system has ended up with hacks to maybe run xmlto<br></div></div>
</blockquote></div><br></div>