[MacPorts] #48499: apache2: httpd binary not available through PATH (apache/passenger does not detect macports apache) (was: which httpd not point to macports apache/passenger not detect macports apache)

[MacPorts]

#48499: apache2: httpd binary not available through PATH (apache/passenger does not
detect macports apache)
----------------------------+--------------------------
  Reporter:  seba.szwarc@…  |      Owner:  ryandesign@…
      Type:  defect         |     Status:  new
  Priority:  Normal         |  Milestone:
 Component:  ports          |    Version:  2.3.3
Resolution:                 |   Keywords:
      Port:  apache2        |
----------------------------+--------------------------
Changes (by ionic@…):

 * owner:  macports-tickets@… => ryandesign@…


Old description:

> on Yosemite when I install apache2 installation goes without problems.
> However command `which httpd` results in: /usr/sbin/httpd
> which means system version of Apache.
> I dont think it is expected behaviour especially when my $PATH looks
> currently like this:
>
> /Users/sebastian/.rvm/gems/ruby-2.2.0/bin:/Users/sebastian/.rvm/gems/ruby-2.2.0 at global/bin:/Users/sebastian/.rvm/rubies/ruby-2.2.0/bin:/opt/local/lib/mysql55/bin:/Users/sebastian/.composer/vendor/bin:/opt/local/bin:/opt/local/Library/Frameworks/Python.framework/Versions/2.7/bin:/Users/sebastian/Skrypty:/usr/texbin:/usr/local/bin:/usr/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/Applications/Server.app/Contents/ServerRoot/usr/bin:/Applications/Server.app/Contents/ServerRoot/usr/sbin:/usr/texbin:/tools:/Users/sebastian/.rvm/bin
>
> I am not sure of this, but this may be also source of problem with
> passenger because for some reason passenger-install-apache2-module
> detects only system version of Apache and denied install module to
> macport version.
> Why macport version is still 2.2 and OSX version is 2.4?

New description:

 on Yosemite when I install apache2 installation goes without problems.
 However command `which httpd` results in: `/usr/sbin/httpd`
 which means system version of Apache.
 I dont think it is expected behaviour especially when my $PATH looks
 currently like this:
 {{{
 /Users/sebastian/.rvm/gems/ruby-2.2.0/bin:/Users/sebastian/.rvm/gems/ruby-2.2.0 at global/bin:/Users/sebastian/.rvm/rubies/ruby-2.2.0/bin:/opt/local/lib/mysql55/bin:/Users/sebastian/.composer/vendor/bin:/opt/local/bin:/opt/local/Library/Frameworks/Python.framework/Versions/2.7/bin:/Users/sebastian/Skrypty:/usr/texbin:/usr/local/bin:/usr/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/Applications/Server.app/Contents/ServerRoot/usr/bin:/Applications/Server.app/Contents/ServerRoot/usr/sbin:/usr/texbin:/tools:/Users/sebastian/.rvm/bin
 }}}
 I am not sure of this, but this may be also source of problem with
 passenger because for some reason passenger-install-apache2-module
 detects only system version of Apache and denied install module to macport
 version.
 Why macport version is still 2.2 and OSX version is 2.4?

--

Comment:

 Thank you for the report. Next time, please also CC the port
 maintainer(s), if any.

 The reason for your problem is easy to explain.

 Take a look at `port contents apache2`.

 You will notice that apache is (mostly) installed in `${prefix}/apache2`,
 with `httpd` as `${prefix}/apache2/bin/httpd`. As far as I know, this has
 been done on purpose to isolate Apache HTTPd versions as much as possible.

 Secondly, MacPorts does have Apache HTTPd 2.4, but it's shipped as a
 separate (and conflicting) port called `apache24-devel`. It is currently
 not considered ready for prime time yet (i.e., replacing `apache2`.) This
 is mostly due to lack of overall interest by Port Developers (and also
 because getting there are some issues involved that aren't easily
 resolved.)

 I'd mark that report as invalid, but am though leaving closure of this
 ticket to the maintainer's hands.

-- 
Ticket URL: <https://trac.macports.org/ticket/48499#comment:1>
MacPorts <https://www.macports.org/>
Ports system for OS X