* William L. Thomson Jr. <[EMAIL PROTECTED]> schrieb:

Hi,

> > 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.

Well, they told me, I won't need them ... who the hell's right ?

> > I had some talks w/ tomcat folks
> 
> Where? Who? Just curious.

[email protected]

> 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.

In other words: tomcat ships lots of bundled third-party packages,
while gentoo takes them from the upstream ?

But then I wonder: if the tomcat folks can simply bundle them in,
why does gentoo has to suffer from these download restrictions ?

> >  - 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.

hmm, we should do some deeper investigations @ [EMAIL PROTECTED] ...

<snip>

> 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.

Oh hell ...

<snip>

> 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.

Okay, since I'm not using it in production yet, I'll try the masked 6.0.6.

BTW: 

What does the jni useflag actually do ? Switch between java and native 
implementation of certain things (SSL, and what else?) ?

And it seems that ecj is used instead of the default java compiler. 
Can't jikes be used instead of ecj (IMHO, should be faster) ?


cu
-- 
---------------------------------------------------------------------
 Enrico Weigelt    ==   metux IT service - http://www.metux.de/
---------------------------------------------------------------------
 Please visit the OpenSource QM Taskforce:
        http://wiki.metux.de/public/OpenSource_QM_Taskforce
 Patches / Fixes for a lot dozens of packages in dozens of versions:
        http://patches.metux.de/
---------------------------------------------------------------------
-- 
[email protected] mailing list

Reply via email to