Opened 12 years ago
Closed 7 years ago
#35824 closed update (fixed)
apache2: Update to 2.4.26
Reported by: | Markus.Ueberall@… | Owned by: | ryandesign (Ryan Carsten Schmidt) |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | |
Keywords: | Cc: | pixilla (Bradley Giesbrecht), BjarneDMat, cooljeanius (Eric Gallager), Ludwig.Huegelschaefer@…, moderndeveloperllc (Mark Garrett), ldl@…, Schamschula (Marius Schamschula), Behinder (behinder), dark.panda+macports@…, chrisminett (Chris Minett), alexwhitewhale (Alexander Romanovich), MacTrophy | |
Port: | apache2 |
Description
Apache2 2.4.x has been around for some time now and does offer a number of improvements.
According to the mailing list, some (extensive) compatibility tests with modules have been executed (and a port file should already be in existence somewhere), but for the last few months, no update (or "devel" port) found its way into the repository...
Attachments (1)
Change History (20)
comment:1 follow-up: 7 Changed 12 years ago by ryandesign (Ryan Carsten Schmidt)
Cc: | pixilla@… macintosh@… added |
---|
comment:2 follow-up: 3 Changed 12 years ago by pixilla (Bradley Giesbrecht)
Ryan: Let me refresh my memory before I answer. I'll try to look it over this evening.
comment:4 Changed 12 years ago by jmroot (Joshua Root)
Cc: | ryandesign@… removed |
---|---|
Owner: | changed from macports-tickets@… to ryandesign@… |
Type: | defect → update |
Version: | 2.1.2 |
comment:5 Changed 12 years ago by Ludwig.Huegelschaefer@…
If I could get a recipe on how to test it, I would invest some time!
comment:7 Changed 11 years ago by moderndeveloperllc (Mark Garrett)
Replying to ryandesign@…:
Bradley, do you think this set of changes is ready to be included in the MacPorts repository?
Just curious if there is any movement on this, or if it's far down the priority list. Thanks.
comment:8 follow-up: 9 Changed 11 years ago by ryandesign (Ryan Carsten Schmidt)
Cc: | Ludwig.Huegelschaefer@… mark@… ldl@… added |
---|
Has duplicate #42226.
Bradley, what would be the best way to move forward? apache24-devel was committed to the main ports tree, but none of the other changes. I don't want to add variants; I just want to replace apache2 with apache24-devel's contents and update all the ports that use apache2 to be compatible with it.
I am not familiar with Mercurial. How would I get a diff of all the changes made in your BitBucket repository, so that I could try to apply them to the current version of the ports in the main ports tree to test them? Or could you make the diff and attach it to this ticket, and I can work on updating it?
comment:9 Changed 11 years ago by ldl@…
Replying to ryandesign@…:
Has duplicate #42226.
Bradley, what would be the best way to move forward?
I have 3 days to make sure a ton of Drupal 6 code will run on PHP 54 and potentially convert the install to Drupal 7.
I got Ryan's apache24-devel hack version to compile and link, but felt that was probably unstable ground to add other PHP ports to, so I downloaded Bradley's local repository and hacked it to include the latest PHP 5.4 and other details.
Got both to compile, and modified config files to load php into apache.
sudo apachectl start gives me this:
httpd: Syntax error on line 169 of /opt/local/apache24/conf/httpd.conf: Cannot load /opt/local/apache24/modules/mod_php54.so into server: dlopen(/opt/local/apache24/modules/mod_php54.so, 10): Symbol not found: _unixd_config\n Referenced from: /opt/local/apache24/modules/mod_php54.so\n Expected in: /opt/local/apache24/bin/httpd\n in /opt/local/apache24/modules/mod_php54.so
Ryan uses this code to set up the php port group:
# Set up the php portgroup, for extension subports. if {[is_extension_subport]} { if {![info exists php.extensions]} { php.extensions ${php.rootname} } php.setup ${php.extensions} ${version}
While Bradley uses this code to set up the php portgroup:
# Set up the php portgroup, for extension subports. if {[is_extension_subport]} { default php.extensions ${php.rootname}
It's over my head how this works and if it matters.
You can do a diff on my portfile with Bradleys to see all changes.
Anyone?
Changed 11 years ago by ldl@…
Composite php portfile. Trying to reconcile Bradley and Ryan's work
comment:10 Changed 11 years ago by ldl@…
I can compile apache24-devel and have got it working.
How hard would it be to simply take the php54 in Bjarne's work and modify it to create php54-devel, compile the current php 5.4.24 and require the apache24-dev version?
That would get the mission accomplished.
Either that or mark the project Abandoned.
comment:12 Changed 9 years ago by ryandesign (Ryan Carsten Schmidt)
Cc: | seba.szwarc@… added |
---|
Has duplicate #50126.
comment:14 Changed 8 years ago by chrisminett (Chris Minett)
Cc: | chrisminett added |
---|
comment:15 Changed 7 years ago by alexwhitewhale (Alexander Romanovich)
Cc: | alexwhitewhale added |
---|
comment:16 Changed 7 years ago by l2dy (Zero King)
Summary: | apache2: Update to 2.4.3 → apache2: Update to 2.4.26 |
---|
comment:17 Changed 7 years ago by oldblue910 (Shawn)
This really needs to get done. Apache 2.2 is ancient and has now been end-of-lifed as of June 2017. I'm not an expert on doing this, or I'd do it myself. I just don't have the time to learn it all. Regardless, this is a big hole in MacPorts support, so hopefully someone can take this on and get apache2 migrated to 2.4. With as many smart people as there are around here, I'm going to go out on a limb and say someone here could get it done in a weekend.
comment:18 Changed 7 years ago by MacTrophy
Cc: | MacTrophy added |
---|
comment:19 Changed 7 years ago by ryandesign (Ryan Carsten Schmidt)
Resolution: | → fixed |
---|---|
Status: | new → closed |
Marius updated apache2 to 2.4.x.
Yes, that's right. As I recall, Bjarne did most of this work, put it into Bradley's Mercurial repository on bitbucket, and told us June 1 2012 that Apache 2.4.x in MacPorts is ready to go and invited us to test it. That was the last I heard, so either nobody found any problems, or nobody tested it. It wasn't just updating the apache2 port; it was also adding an apache2 portgroup, and modifying many ports to use that portgroup and in other ways be compatible with the new apache2. Bradley, do you think this set of changes is ready to be included in the MacPorts repository?