Bjarne D Mathiesen wrote: > OK - I'm trying to update the apache2 portfile from 2.2.22 to 2.4.2
pixilla & I have been working on this for some time now. The state is presently as follows: apache2 @2.4.2 www/apache2 php5 @5.3.13_0+apache2+pear+suhosin (active) php5-mysql @5.3.13 php/php5-mysql -> works on test server for the last month -> works on production server for the last month mod_antispam @1.0 www/mod_antispam -> seems to be abandoned by creator -> doesn't install -> serious work needs to be done -> no response from maintainer -> anybody using this ... then yell _loudly_ mod_authn_otp @1.1.1 www/mod_authn_otp -> no problems detected when installing -> no response from maintainer mod_cband @0.9.7.5 www/mod_cband -> works with simple search/replace pathc -> no response from maintainer mod_chroot @0.5 www/mod_chroot -> no problems detected when installing -> no response from maintainer mod_dnssd @0.6 www/mod_dnssd -> no problems detected when installing -> no response from maintainer mod_dosevasive @1.8 www/mod_dosevasive -> replaced by mod_evasive mod_evasive @1.10.1 www/mod_evasive -> works with simple search/replace pathc -> no response from maintainer -> works on my production server mod_fastcgi @2.4.6 www/mod_fastcgi -> doesn't install -> should be replaced by mod_fcgid -> anybody using this ... then yell _loudly_ mod_fcgid @2.3.7 www/mod_fcgid -> no problems detected when installing mod_gnutls @0.5.10 www/mod_gnutls -> works with simple search/replace pathc -> no response from maintainer mod_jk @1.2.27 www/mod_jk mod_jk2 @5.5.4 www/mod_jk2 -> not relevant for apache httpd 2.4.2 -> ought to retired completely mod_mono @2.10 www/mod_mono -> works with simple search/replace pathc -> no maintainer at present mod_perl @1.30 www/mod_perl -> not relevant for apache httpd 2.4.2 -> ought to retired completely mod_perl2 @2.0.6 www/mod_perl2 -> works with patches made by pixilla -> works with perl5.14 mod_proxy_html @3.0.1 www/mod_proxy_html -> not relevant for apache httpd 2.4.2 -> module already included by apache -> ought to retired completely mod_python @3.3.1 www/mod_python mod_python25 @3.3.1 www/mod_python25 mod_python26 @3.3.1 www/mod_python26 mod_wsgi @3.3 www/mod_wsgi mod_ruby @1.3.0 www/mod_ruby -> no work has been done on these -> maintainers haven't responded -> ought to be considered abandoned by maintainers -> anybody using these ... then yell _loudly_ !!! mod_security @1.8.6 www/mod_security -> ought to replaced by mod_security2 mod_security2 @2.6.5 www/mod_security2 -> no problems detected when installing -> works on my production server mod_ssi_func @1.0 www/mod_ssi_func -> not relevant for apache httpd 2.4.2 -> ought to retired completely ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ So ... where do we go from here ??? We've got patches etc for the above and I've got it running completely without any problems on both my test system as well as in production. Ryan is of the opnion that we transition _hard_ from 2.2.x to 2.4.x and don't look back at all. Are there any outstanding stuff / ports that will have problems with the transition from 2.2.x to 2.4.2 before we do so ??? :-) -- Bjarne D Mathiesen København N ; Danmark ; Europa ---------------------------------------------------------------------- denne besked er skrevet i et totalt M$-frit miljø MacOS X 10.7.3 Lion ; 2.8GHz Intel Core i7 ; 16GB 1067MHz DDR3 _______________________________________________ macports-users mailing list [email protected] http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
