> > > On 2015/04/21 21:34, Stefan Sperling wrote: > > > > How about... we just remove apache-httpd-openbsd? > > > > > On Tue, Apr 21, 2015 at 08:57:28PM +0100, Stuart Henderson wrote: > > > That is a medium-term goal, but there's a bit of work to do first. > > > On Mon, May 11, 2015 at 07:34:10PM +0200, Stefan Sperling wrote: > > I've also received off-list objections to removing apache-httpd-openbsd.
It doesn't impact this diff, but we could later rename apache-httpd-openbsd files and go back to the standard names for apache2 and get rid of the manpage patches. Or fix the manpages to add the suffix and feed it upstream instead. > > Here's a new diff which updates apache-httpd to 2.4 without conflicting > > with apache-httpd-openbsd. > > > > So far, I've tested packaging of all dependent ports except for lang/php/ > > Works except for the following ap2- modules which stop building: > > ap2-mod_fastcgi > > ap2-mod_fcgid > > Haven't investigated why yet. Perhaps these just need a version upgrade? On 2015/05/11 20:08, Claudio Jeker wrote: > Hmm. I think these modules have been superseeded by mod_proxy_fcgi which > is part of apache 2.4. Which is one of the reasons I started going down > this road. So maybe the way to go is to remove these two ports and tell > people to change their config to use mod_proxy_fcgi. That sounds like the right approach to me. If php still works (highly likely to, but better check) then I think we should go ahead.