On Sat, 2006-12-23 at 20:20 +0100, Enrico Weigelt wrote: > > Great :) > It was really, really ugly getting tomcat emerge'd w/ all this > commercial crap :(
Blame upstream for using them. Granted the are somewhat optional more on that below. > I had some talks w/ tomcat folks Where? Who? Just curious. There are ant download targets for most of the deps, we just bypass. So it's not like the deps come from no where in a normal build from source. > - they were some bit confused > about the huge dependencies @gentoo and suggested using some > of their (monolithic) packages instead. I have tried to slim it down, but dropping certain deps to seem to change things that are activated or not within Tomcat. For example there seems to be some issues with the java5 USE flag. Either that, or some of the dropped deps when that flag is used is effecting the resulting catalina.jar. Who knows what other jars would be effected by dropping other deps. > Could anyone explain where all these dependencies come from ? Tomcat <=5.5.x has a ton of deps. There are these wonderful deps referred to in build.properties.default as Core Optional Libraries. I hate who ever decided to word it that way or call it that ;) I have tired to research if they are needed, what they do etc. If they effect the ending result. Example core optional libraries. Log4j? What's up with that Tomcat 5.5.x uses JULI by default. So that one alone I have yet to figure out why it's needed or should be around. Now consider this for a moment. Upstream is likely using binaries to build their binary version of Tomcat ;) So it's not like they are compiling all the stuff they are using to build Tomcat from source. Before they compile and ship Tomcat. We do it all from source. :) Which can explain extended deps right there. > Are there perhaps some build conditionals which are not yet > reflected in useflags ? I highly doubt it and with all the variables, you would likely break something and not know it. Till someone uses that feature or aspect and etc. Most are expecting the compiled from source on Gentoo version to be equivalent to the binary version, out of the box. The only thing I can say about the whole situation is they are working on releasing Tomcat 6.0.x in the next month or two. Tomcat 6.0.x has way less deps, and it's much clearer that the ones it has are needed. No core optional, or optional stuff. I might see about unmasking and versioning either alpha/beta the ebuild despite sources not being tagged :( So people can test it out and hopefully help get it released ASAP. As for 5.5.x, it's not clear if there will be further releases from upstream. It's got lots of legacy code and likely deps. -- William L. Thomson Jr. Gentoo/Java
signature.asc
Description: This is a digitally signed message part
