My preference would be to:

- Make building.html a overview of links to build the appropriate tomcat version
- Move the existing building.html instructions to jakarta-tomcat-5 as BUILDING.txt. O wait, its already there ;)
- Add the "lazy" build script wrapper to jakarta-tomcat-5. Tweaking the script to handle the issue of possibly being run while inside the jakarta-tomcat-5 repository. (Because in its current form would check out another jakarta-tomcat-5 repository)


This way if tomcat 5.2 comes along and has a drastically different build process - then http://jakarta.apache.org/tomcat/building.html would point to the appropriate CVS branch BUILDING.txt.

OTOH, the above suggestion could be worthless since there is a nightly nag done via gump(?) so maybe the answer is to ignore the above and make the wrapper script around the gump descriptor.

At a minimum, it might be a good idea to get rid of building.html and have it link directly to the CVS version (BUILDING.txt) so there are not 2 copies of the same instructions.

(And there is one last option which is to do nothing ;) )

-Tim

Remy Maucherat wrote:
Tim Funk wrote:
I would be in favor of adding a link to jakarta-tomcat-site to point to the viewcvs.cgi version so the script can be easily downloaded whichout extra user effort.


In theory, there was that (http://jakarta.apache.org/tomcat/building.html) which was supposed to be similar.

What do you think ?

Remy



--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to