Apache2 rev bump for OpenSSL update

[Jim Jagielski]

As a macports maintainer myself, as well as someone who is on the Apache httpd project itself, I volunteer to help out with this. 

--
Jim Jagielski
Brief? Mobile

> On Mar 3, 2016, at 7:29 PM, Marius Schamschula <lists at schamschula.com> wrote:
> 
> I agree that it’s time to do something about apache. The ticket bellow is four years old, and I added myself to the CCs 21 months ago…
> 
> As someone that has used apache 2.4.x since 2012 (my old hmug.org builds), and under MacPorts as apache24-devel for over two years (although I’m down to a single machine using it, and I may end up replacing it with nginx), it boggles my mind that Apple has been shipping apache 2.4.x with OS X since Yosemite, and MacPorts is still stuck at 2.2.x.
> 
> Using apache24-devel with php is somewhat complicated, as building the php-apache2handler against apache24-devel requires me to maintain my own branch of php, as php-apache2handler forces apache2 to be installed. Having apache24 would make this easier for others. I have not had any luck getting php-fpm to work with apache24-devel, though it works nicely with nginx.
> 
> Of course, all my Linux and FreeBSD machines use apache 2.4.x, and I like consistency in server setup.
> 
> On Mar 3, 2016, at 5:54 PM, Bradley Giesbrecht <pixilla at macports.org> wrote:
> 
>>>> On Mar 3, 2016, at 12:09 AM, Juan Manuel Palacios <jmpp at macports.org> wrote:
>>>>> On Mar 3, 2016, at 3:35 AM, Ryan Schmidt <ryandesign at macports.org> wrote:
>>>>> On Mar 3, 2016, at 00:18, Juan Manuel Palacios <jmpp at macports.org> wrote:
>>>>> 
>>>>> Apache 2 rev-bumped, cf. r146274.
>>>>> 
>>>>> On a side note, and if I may in this same thread, do we have any policy for not moving the Apache 2.4 port out of “dev”?  Not too sure when it became the recommended release series by the ASF, but it certainly isn’t dev any longer.
>>>> 
>>>> There's a ticket you can read. We can't just replace the current apache2 port with the current apache24-devel port because it also changes the directory layout.
>> 
>>> 
>>> Yeah, that I understand, we keep versioned ports for other packages too, e.g. mysql55, mysql56, mysql57, and other examples. And we don’t replace one with the other for a myriad of reasons.
>> 
>> With versioned apache24 modules like apache24-mod_python27.
>> 
>>> So we could deprecate the apache24-devel port and create apache24, maybe even also deprecating apache2 and eventually replacing it with apache22, which needless to say would be compatible with the former, and would live on in parallel to apache24, just as mysql55 does to mysql56, etc.
>>> 
>>> You have a URL for that ticket that you mention?
>> 
>> https://trac.macports.org/ticket/35824
>> 
>> —
>> Brad
>> 
>> _______________________________________________
>> macports-dev mailing list
>> macports-dev at lists.macosforge.org
>> https://lists.macosforge.org/mailman/listinfo/macports-dev
> 
> Marius
> --
> Marius Schamschula
> 
> 
> 
> 
> _______________________________________________
> macports-dev mailing list
> macports-dev at lists.macosforge.org
> https://lists.macosforge.org/mailman/listinfo/macports-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.macosforge.org/pipermail/macports-dev/attachments/20160303/ae839e38/attachment-0001.html>