Apache 2.4.28 update today? (was:Re: Apache 2.4 any time soon?)

Marius Schamschula lists at schamschula.com
Mon Oct 16 10:57:54 UTC 2017


> On Oct 15, 2017, at 10:04 PM, Bill Christensen <billc_lists at greenbuilder.com> wrote:
> 
> 
> 
> On Sun, Oct 15, 2017 at 6:30 PM, Marius Schamschula <lists at schamschula.com <mailto:lists at schamschula.com>> wrote:
> Bill,
> 
> You are welcome, I’ve spent the last couple weeks making sure all the dependencies build. There still are a few loose ends:
> 
> 1) There is no automatic migration tool for folks that had the old apache2 2.2.x installed. This is something that never bothered me, as I heavily edit https.conf,
> 
> I suspect that you mean the httpd.conf,  right?  

Yes.

>  
> and use the default macOS htdoc path.
> 
> I don't... 
> 
> I'd heard that a number of things have moved around.  I don't see anything on that in the changelog 
> 
> http://svn.apache.org/viewvc/httpd/httpd/branches/2.2.x/CHANGES?view=markup <http://svn.apache.org/viewvc/httpd/httpd/branches/2.2.x/CHANGES?view=markup>
> 
> Anything specific I  should watch for?
> 

Well, the old apache2 installed everything under ${prefix}/apache2, which violated the MacPorts tree. The new version installs things under:

1) configuration - ${prefix}/etc/apache2/

2) data - ${prefix}/www/

3) binaries -   ${prefix}/sbin

4) modules -  ${prefix}/lib/apache2/modules

I had meant add a note to the Portfile. I will add this.

> I do the same for nginx.
> 
> 2) I just noticed that any dependent port that uses apr-util may not cleanly build (I just fixed mod_qos) because my local apr-util was built with the no_bdb variant, masking a missing library path for BerkeleyDB 4.8 (${prefix}/lib/db48).
> 
> Please let me know if there are any issues
> 
> Will check it on a test server first and will let you know.
> 
>  
> 
>> On Oct 15, 2017, at 6:07 PM, Bill Christensen <billc_lists at greenbuilder.com <mailto:billc_lists at greenbuilder.com>> wrote:
>> 
>> Hey folks,
>> 
>> Running my daily updates,  I see:
>> 
>> The following installed ports are outdated:
>> 
>> apache2                        2.2.34_0 < 2.4.28_0
>> 
>> 
>> 
>> Thanks Marius Schamshula and Daniel Luke (and anyone else who was part of this) for pushing this boulder up the last bit of the hill!
>> 
>> 
>> 
>> 
>> 
>> 
>> On Tue, Aug 22, 2017 at 8:42 AM, Daniel J. Luke <dluke at geeklair.net <mailto:dluke at geeklair.net>> wrote:
>> On Aug 22, 2017, at 7:51 AM, Rainer Müller <raimue at macports.org <mailto:raimue at macports.org>> wrote:
>> > On 2017-08-12 01:52, Bill Christensen wrote:
>> >> I see that Apache 2.2 officially hit EOL as of the latest release
>> >> (7/11/17).
>> >>
>> >> Any chance we'll see an Apache 2.4 for production in MacPorts in the
>> >> near future?
>> >
>> > It is already in the ports tree as apache24-devel. As the corresponding
>> > ticket for making Apache 2.4 the default got no attention from Ryan as
>> > maintainer yet, I assume help and patches to make this work would be
>> > appreciated.
>> >
>> > https://trac.macports.org/ticket/50965 <https://trac.macports.org/ticket/50965>
>> 
>> IIRC Ryan wanted to tie the apache port install layout changes to the upgrade to 2.4. I think we can do upgrade to 2.4 and layout changes separately (especially if that's still what's holding up the upgrade).
>> 
>> --
>> Daniel J. Luke
>> 
>> 
>> 
>> 
> 
> Marius
> --
> Marius Schamschula
> 
> 
> 
> 
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macports.org/pipermail/macports-users/attachments/20171016/cc950006/attachment.html>


More information about the macports-users mailing list