----- Original Message ----- > From: André Warnier <a...@ice-sa.com> > To: Tomcat Users List <users@tomcat.apache.org> > Cc: > Sent: Monday, July 18, 2011 8:33 AM > Subject: Re: RedHat and mod_jk > > Christopher Schultz wrote: >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA1 >> >> Mark, >> >> On 7/16/2011 12:50 AM, Mark Eggers wrote: >>> I've been successful in the past in getting permission to build > critical components locally. I've also been in environments where this was > strictly forbidden, even at the expense of not meeting business requirements > and/or exposing the infrastructure to known security risks. Meeting > requirements > is preferred (in my book). >>> >>> It also appears that more and more admins are uncomfortable with > building, installing, and then managing systems with locally installed > software. > This goes back to the challenge that the >>> original poster had. Why an admin would balk at learning how to do >>> this is another question . . . >> >> Fortunately for me, I'm the admin *and* I get to make these kinds of >> decisions. >> >> I just don't feel like keeping MySQL up-to-date myself. :) >> > > A reason why admins "balk" may be because they are asked to take care > of more and more systems (due to virtualisation e.g.), and can no longer > afford > to spend the time to do that. > > Anyway, whatever their reasons, a number of admins will not do it, and the > practical consequence in this case will be a decrease of the usage of mod_jk. > > The basic point is : mod_jk is not included in the RedHat standard > Apache/Tomcat > packages. > But maybe this is just an oversight of RedHat, and maybe with a little nudge, > they may be persuaded to include it again. > Does anyone know how one would go about trying to nudge them in this > direction ? > > Alternatively, what would it take for mod_jk to be (maybe again) part of the > standard Apache httpd distribution ? (so that these "packagers" would > include it in the next Apache httpd packaged version without even having to > think about it).
I noticed that it's not a part of the Fedora (basically RedHat's test platform) distribution either. If it's a part of the Apache HTTPD distribution, more Linux distributions might pick it up. Just glancing at my installation, it seems that modules not shipped with Fedora's packaging are modules that are separate from Apache HTTPD (with the notable exception of mod_ssl). For RedHat, the process is roughly: 1) Get the new code accepted upstream. 2) Get it included in Fedora. 3) Get it included in Red Hat Enterprise Linux. This is taken from a RedHat magazine article, and discusses bug fixes, new features, and new packages. I'm guessing that item 1) applies to bug fixes and new features. So, possibly getting the Fedora team to accept an RPM for mod_jk would be the place to start. They'll probably want a 32-bit, 64-bit, and source packages. They'll also probably want a maintainer for those packages. The IRC channel #fedora-devel on FreeNode might be a good place to start. I don't know how other distributions are handled. Chris, I'm just a lowly systems architect (have been an admin in a former life). Building MySQL was always low on my list of things to do. However, it never seemed as difficult as building PHP :-p. Andre, managing lots of configurations is a pain. I've used custom processes/tools as well as commercial tools. Nothing seems to work effortlessly ;-). So mod_jk builds may be the (very lightweight) straw that breaks an admin's back. . . . . just my two cents. /mde/ --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
