Opened 8 years ago

Closed 8 years ago

Last modified 8 years ago

#50126 closed request (duplicate)

when apache24 will be available?

Reported by: Behinder (behinder) Owned by: macports-tickets@…
Priority: Normal Milestone:
Component: ports Version: 2.3.4
Keywords: Cc: ryandesign (Ryan Carsten Schmidt), BjarneDMat, pixilla (Bradley Giesbrecht)
Port: apache24

Description

C'mon guys. It's included by default in OSX, and also I see this in homebrew for many months. Why Macports still claims 2.4 it is not stable? As far as I see PHP70 not working with 2.2 and I prefer my Apache independent of system Apache.

Change History (7)

comment:1 in reply to:  description ; Changed 8 years ago by ryandesign (Ryan Carsten Schmidt)

Cc: ryandesign@… macintosh@… pixilla@… added

Replying to seba.szwarc@…:

C'mon guys. It's included by default in OSX, and also I see this in homebrew for many months. Why Macports still claims 2.4 it is not stable?

When we made the apache24-devel port we took the opportunity to improve the filesystem layout. Unfortunately this means it's an involved process of making it replace the existing apache2 port because it requires changes in every port that uses apache2. I have not been working on this and would invite the other maintainers of apache24-devel to do this. I think there may be a work in progress in someone's github repository...

As far as I see PHP70 not working with 2.2 and I prefer my Apache independent of system Apache.

I'm not aware of this problem; please file a separate ticket with details and I'll look into it.

comment:2 Changed 8 years ago by danielluke (Daniel J. Luke)

I think at this point, it would be reasonable to push apache24 as the default apache (with the current filesystem layout). There's no reason why both the version upgrade and filesystem layout changes have to happen at the same time.

comment:3 in reply to:  1 ; Changed 8 years ago by Behinder (behinder)

I created ticket #50145 Do you need some additional attachments?

Last edited 8 years ago by ryandesign (Ryan Carsten Schmidt) (previous) (diff)

comment:4 in reply to:  3 Changed 8 years ago by ryandesign (Ryan Carsten Schmidt)

Resolution: duplicate
Status: newclosed

Replying to dluke@…:

I think at this point, it would be reasonable to push apache24 as the default apache (with the current filesystem layout). There's no reason why both the version upgrade and filesystem layout changes have to happen at the same time.

Duplicate of #35824.

Replying to seba.szwarc@…:

I created ticket #50145 Do you need some additional attachments?

I'll respond there.

comment:5 in reply to:  2 ; Changed 8 years ago by ryandesign (Ryan Carsten Schmidt)

Replying to dluke@…:

I think at this point, it would be reasonable to push apache24 as the default apache (with the current filesystem layout). There's no reason why both the version upgrade and filesystem layout changes have to happen at the same time.

It's not just the directory layout. Bradley's branch referenced in #35824 also attempts to deal with the problem of Apache module ports that do not build with Apache 2.4.x.

comment:6 Changed 8 years ago by Behinder (behinder)

So is there any roadmap and time schedule for Bradley's work? If I have to wait another 2 years I would prefer to know sooner, to switch my tools for Brew or Nix.

comment:7 in reply to:  5 Changed 8 years ago by danielluke (Daniel J. Luke)

Replying to ryandesign@…:

It's not just the directory layout. Bradley's branch referenced in #35824 also attempts to deal with the problem of Apache module ports that do not build with Apache 2.4.x.

Those module ports should just be changed to build with apache22 (if we keep it) or removed unless/until a maintainer patches them.

Note: See TracTickets for help on using tickets.