On Sun, 2006-08-20 at 13:43 -0700, Costin Manolache wrote: > If you want to include the real tomcat in gentoo - please use the official > label, follow the same procedure as > our release,
We do include the "real" Tomcat. Problem is aspects of Tomcat many other apps use. With regard to Jasper I believe it's just Jetty. But servlet-api, a bunch of packages depend on that one. How we version the servlet-api is still up for discussion. Since it's not really based on Tomcat versions. Jasper is another story, and Jasper's package version is likely to stay that of the version of Tomcat it came from. Source wise. > and make sure the result of emerge is identical with what the > user would get if he > would get tomcat from ASF. For the most part were are there, short of one jar, naming-factory-dbcp.jar. However it's possible that Tomcat's on Gentoo could be built with newer versions of dependencies/bundled jars. > If you have to patch - and the patch alters the > structure or behavior - please don't call the result 'tomcat' :-) We do not modify Tomcat at all. The only patches are to like not download/compile etc jars that are dependencies of Tomcat, or will be bundled. We link those in since they will already exist on the system as a dependency of Tomcat. Beyond that the only thing the patches do is modify/exclude some targets. Since they lack any sort of condition that would allow a command line option for ant to control if those aspects are built. Like examples, docs, etc. We have use flags, if someone does not set examples, docs etc. We do not build/compile that stuff, much less install it. So our patches do not really modify Tomcat at all. Slight modifications to build.xml files only, and to control what get's built when, how, and with what. -- William L. Thomson Jr. Gentoo/Java
signature.asc
Description: This is a digitally signed message part
