>Hi Vic. We're currently trying to sort out the best way of >packaging a 4.0 RPM.
>TC4 has quite a few external jar dependencies ... some optional, some >mandatory. We're kind of between a rock and a hard place with >both a few of the >RPM packaging policies as well as some jar redistribution issues. I'm still waiting for Craig answer on externals jars avaibility outside Sun site (jta, jmx, ldap, ....). I've asked to have them all of them in a tomcat-supplemental tarball available on jakarta.apache.org to have them included in TC 4.0 RPM, of course if license permit that also. Something to be validated by Sun Lawyers. The interest of the RPM is that it provides a ready-to-run solution but it won't be the case if the users need to grab and then install (where) the external jars by hand. Some could think we could get the TC 4.0 binary and package it in RPM but it's also not a solution since RPM policies ask to have a binary generated from one or many sources and in that case it won't be the case. Only some vendors provide RPM like this, JDK/SDK from Sun/IBM for example but these tools are not OpenSource... Until I got a positive answer from Craig, I'll have to delay TC 4.0 RPM (allready done in-house) and I'm more than sorry about that.....
