On Fri, Apr 10, 2009 at 6:32 PM, Chris Darroch <chr...@pearsoncmg.com>wrote:
> Hi -- > > Jeff Trawick wrote: > > Many people use mod_fcgid on Apache 2.0/2.2. The message should be that >> mod_fcgid development has moved to the ASF, and existing users are not being >> left behind in the transition. So a branch for mod_fcgid 2.x is maintained >> for httpd 2.0/2.2 users just as our own stable branches are maintained (FAR >> beyond emergencies, at least for 2.2.x). >> >> This isn't necessarily in opposition to what you said, but some might read >> it as something like "Apache took over and they won't distribute fixes that >> work with my existing configurations except in extreme circumstances." >> > > I think that's something we want to avoid. (Sorry for the slow > response; I'd like to say I've been giving this deep thought but > actually I've just been distracted with other work for a bit.) > > It's also worth assuming, I think, that mod_fcgid isn't going > to be back-ported and included in the 2.2.x distribution anytime soon. sure; IMO it doesn't ever need to be included in the 2.2.x distribution > > > Given that, I suppose we should look at continuing a 2.x branch > for mod_fcgid (with improved autoconf magic, obviously), at least > until a httpd 2.4.x is released with mod_fcgid in it. > > It's slightly inconvenient but I'll willing to start digging into > the autoconf stuff and generally trying to get a branch going > before we add it into httpd trunk. How do others feel? As I understand it, the current state of mod_fcgid is that it has been imported into the httpd project's mod_fcgid subtree, it has been cleaned up w.r.t. licensing and coding style and some other concerns (what's in readme vs. other files), but no real code changes have been made. Can we * import the cleaned up mod_fcgid into httpd trunk for expected inclusion in the next httpd release (2.4 or 3.0 or whatever it is) ** work on autoconf and incompatible code changes there (httpd trunk) ** if for some reason this work doesn't proceed fast enough for mod_fcgid to be included in the next httpd release, it can be axed from the future httpd 2.4/3.0/whatever branch when that branch is created * use the httpd/mod_fcgid subtree for bug fix releases of mod_fcgid (retain compatibility with httpd 2.0/2.2 as well as existing mod_fcgid configurations)
