tisdagen den 12 november 2002 11.12 skrev Jean-Michel Dault: > > > Ultimately, I was trying to get mod_jk2 and tomcat4 running with > > > apache2, but I gave up. > > Tomcat is not obvious to compile. There are *lots* of requirements to > build it, grousse and hgomez could tell you more ;-) > > > > It might help if mod_jk2 was provided in mdk, but jpackage and apache > > > provide apache2 and mod_jk rpms, so I'm not sure who is creating the > > > incompatiblities here, i.e. if it's not just better to go with their > > > apache2 rpm for Java, but clearly we don't want to turn Java developers > > > away from mdk, but I don't know what the best solution is. > > Basically, all Apache modules have to match the Apache version they were > built for. This means that if you install ADVX, you have to recompile > mod_jk2 for ADVX. If you install the regular Apache generic RPM, you > have to install the generic mod_jk2 RPM. > > So, if you want to run apache+php+ssl+perl+the-73-other modules, right > now, you will have to recompile mod_jk2. > > If you only want to run Apache + mod_jk2, install the generic versions. > > > Me neither... I could try make this work but I know nothing about java. > > It's also difficult since java is propetary and needed _also_ when > > building... This has of course the effect that none of these possible > > future packages can live in contribs. > > There is something that we could do. If we had a mod_jk.src.rpm, and a > mod_jk2.src.rpm, so we can only rebuild this part, that could work. > > However, if we want to provide full Tomcat support for Mandrake, we > would need: > mod_jk1 for Apache 1.3 in 9.0 > mod_jk1 for Apache 1.3 in Cooker > mod_jk1 for Apache 2.0 in 9.0 Contribs > mod_jk1 for Apache 2.0 in Cooker Contribs > mod_jk2 for Apache 1.3 in 9.0 > mod_jk2 for Apache 1.3 in Cooker > mod_jk2 for Apache 2.0 in 9.0 Contribs > mod_jk2 for Apache 2.0 in Cooker Contribs > Plus one version each time Vincent makes a security update...
Phuh!, what a nightmare. I think this could be possible for "a closed source" binary only, club or mdk enterprise edition cd. But then a real java guru needs to fiddle with this I belive. If your marketing department think they can sell it, so why not try. > Of course, we can choose what we want to support. We could decide to > support only Apache 2.0 and mod_jk2. But then, I would get hundreds of > complaints from people running Apache 1.3 with mod_frontpage or > mod_auth_external, who have not been ported to 2.0 yet, and are in use > by several big ISPs. apache2-mod_auth_external-2.0.43_2.2.1-*mdk is in contribs. > *Sigh*.. It's hard to please everyone =( He he, yes. -- Regards // Oden Eriksson, Deserve-IT Networks Check the "Modules For Apache2" status page at: http://www.deserve-it.com/modules_for_apache2.html
