Hi, I noticed, that we could standardize a bit more on the tool chain used for releasing mod_jk.
1) Building configure During the release process, the configure script gets build, which uses autoconf, automake, m4 and libtool. In the last year or so I used autoconf: 2.60 automake: 1.9.6 m4: 1.4.4 libtool: 1.5.22 The latest releases are: autoconf: 2.61 automake: 1.10 m4: 1.4.8 libtool: 1.5.22 I will update my toolchain to the versions listed above. I think it's not really necessary to always use the latest version, but we should try to not fall too much behind them. 2) Extracting plain text from html For extracting the text files CHANGES and NEWS from the docs, we also use one of the tools w3m, links or elinks, whichever is found on the build machine. The resulting formats seem to differ, so I would prefer to stabilize on one of them. w3m and elinks seem to be not very active (w3m no releases at all, elinks once a year). There is a follow-up project on links http://links.twibright.com. It is under GPL, but for simply running it, that's OK. I used version 2.1pre22, the latest one is 2.1pre26 (November 2006). Jean-Frederic: which of the three tools did you use? The output format differs a little and your tool produced automatic reference lists, which could be useful but in our case produced non-usable references to the file system on the build machine at the end of the NEWS file. Regards, Rainer --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
