[MacPorts] #21315: Apache2 install location does not seem to conform as well as it could to MacPorts installation directory guideline
MacPorts
noreply at macports.org
Fri Sep 11 14:27:03 PDT 2009
#21315: Apache2 install location does not seem to conform as well as it could to
MacPorts installation directory guideline
------------------------------+---------------------------------------------
Reporter: scott@… | Owner: macports-tickets@…
Type: defect | Status: new
Priority: Normal | Milestone:
Component: ports | Version: 1.8.0
Keywords: | Port: apache2
------------------------------+---------------------------------------------
Changes (by ryandesign@…):
* cc: imajes@… (added)
* port: => apache2
Comment:
Replying to [comment:4 scott@…]:
> My suggestion would be to follow the Apache 2 layout that Apple
provides, but use prefix as "root".
[snip]
> The rest of the parts follow the same pattern.
Looks totally logical to me.
> I think some discussion would need to be made as to where the actual
http docs files live, if they live in prefix somewhere, or if they were to
be pointed to /Library/WebServer/Documents. That I am not sure what would
be the most logical structure to follow.
Should not be outside of ${prefix}. My vote is for ${prefix}/www/${name}
which is where other web ports should be installing things I think. The
DocumentRoot should possibly be set to something like ${prefix}/www/htdocs
(usual apache naming) or ${prefix}/www/public (Zend Framework naming),
possibly with nothing at all installed in that directory.
> This all makes a lot of sense to me. I can see some resistance, as a
lot of people are going to like the "clean" all in one place method.
I'm not sure why apache2 currently does it the way it does it. I'm not
convinced it's because it was considered to be cleaner. James, do you
remember?
--
Ticket URL: <http://trac.macports.org/ticket/21315#comment:5>
MacPorts <http://www.macports.org/>
Ports system for Mac OS
More information about the macports-tickets
mailing list