Martin> It would be further good if all the release engineers Martin> (moiself, Vin, and Andreas) would do this in an automated Martin> fashion for every release. Mats> Might be good but is it really necessary to test with all Mats> versions. If the main purpose with the CVS archive is to Mats> build the packages it would be enough to use one set of Mats> tools, the last stable ones. No, lots of people use the CVS archive, for various reasons. Since we don't supply the texinfo tools, we need to treat them like we treat compilers. We should not force people who happen to want XEmacs features available only in the development series to update their working systems too (and with package-manager-based linux distros, updating one package can cause cascades of updates throughout the system). Unfortunately, GNU doesn't care---"since it's free, there's no cost to updating, so _we_ don't have to care about backwards compatibility." (That's a little unfair, but backwards compatibility has never been a high priority at GNU.) What Martin is aiming at is an excellent thing. Once he has the scripts in place, it's just a matter of a little more CPU time and a little more disk space for a few maintainers. -- University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN Institute of Policy and Planning Sciences Tel/fax: +81 (298) 53-5091 _________________ _________________ _________________ _________________ What are those straight lines for? "XEmacs rules."