> > Hey, you did a great job! =) It ticks! I owe you a couple of beers ;-) > I take that as a promise :-)
Now, I only have to find out how to send alcohol to Sweeden without it being confiscated at customs... Otherwise, I'll have to bring them myself ;-) > > Not until mod_perl and mod_php are stable enough. There are many issues > > right now, such as PHP pages remaining in browser cache, Apache-ASP, > > HTML-Embperl, Apache-SSI and Akxit not working. > Ohh..., shit! I didn't know that..., I've been away from computers for some > time hunting. Is it really _this_ serious?!?!?!?! It *is* serious. Many e-commerce sites use some perl modules heavily, and if they don't work, they can't upgrade. > > Thse are serious issues since PHP is used by 38% of websites and > > mod_perl by 36%. > netcraft percentage? Yup, it was published in the latest Apache Week. > > I think these issues will be fixed in the following months, until then, > > Apache 2.0 will remain in the Contribs. > Okidoki. > > BTW. I just went through your patches for the apache2 modules I > submitted..., out of curiosity..., _how_ did you know what to fix? Most of the patches concern component registering, ie: putting the version of the module in the Apache version. This is needed for testing, otherwise we don't know if the module was loaded properly. These patches were made by myself, it's not hard when you know the API enough ;-) The other patches concern linking additional libraries, like libmysqlclient. In this case, you have to use "ldd" to make sure the libraries are linked correctly, and "nm" to find out what symbols are missing. Jean-Michel
