On Sat, Jul 6, 2013 at 6:35 PM, Armin K. <krejzi@email.com> wrote:

Hello,

I've wondered why no one upgraded Apache to 2.4 after being available for so long. Then I stumbled upon an answer on this list where it has been said that 2.4 breaks too many packages [1].

I've taken some time to verify what does it break, and fixed all packages from [extra] and [community] which had direct dependency on the "apache" package (mod_whatever ones).

The mod_fcgid, mod_wsgi2 and mod_wsgi just need simple rebuilds against newer versions.

PHP case was somehow strange. I had to modify some configure switches. Without --disable-cgi I'd get undefined references at build time and without --with-apsx=/usr/bin/apsx I'd get undefined references at run time.

For other ones, I've found patches online and assembled them for direct applying in Archlinux svn (I used svn add and svn diff)

In case someone is interested, patches can be found at [2]. It's free hosting, so it might "suck" sometimes.

I've tested the packages against apache24 package from AUR. By tested, I mean compiled, loaded into httpd and checked that httpd doesn't fail to start.

As a side note, apache24 uses event_mpm by default, but you might need to change to prefork one to use PHP module. Also, with apache 2.4 you can use php-fpm via mod_proxy as described at [3]

As for the perl module, I had to use svn checkout of the httpd24 branch. Patch was getting way to big to ship in package.

Regards

[1] https://mailman.archlinux.org/pipermail/arch-general/2012-October/031777.htm... [2] http://blackprince.net63.net/apache24/ [3] https://wiki.apache.org/httpd/PHP-FPM

I think the package in the repositories should be renamed to apache22 considering how long it has been out-of-date. If a developer or trusted user doesn't want to maintain apache 2.4 in the repositories, that's fine, but we shouldn't be reserving the name.

Am 11.07.2013 15:45, schrieb Armin K.:

...

As a side note, apache24 uses event_mpm by default, but you might need to change to prefork one to use PHP module. Also, with apache 2.4 you can use php-fpm via mod_proxy as described at [3]

As for the perl module, I had to use svn checkout of the httpd24 branch. Patch was getting way to big to ship in package.

Regards

[1] https://mailman.archlinux.org/pipermail/arch-general/2012-October/031777.htm... [2] http://blackprince.net63.net/apache24/ [3] https://wiki.apache.org/httpd/PHP-FPM

Using php-fpm with mod_proxy_fastcgi sounds interesting. Personally, I don't care whether mod_php breaks or not, since using fpm even on small installations seems like the superior method.

Sigh, no one seems to care. Well, nothing strange. Patches will remain on the site in case someone needs them.

You might try to write an email to jgc directly, since I have no idea if he reads arch-general at all. He stated in the past that "nothing works with Apache 2.4", I have no idea if your post will convince him otherwise.