apache2 location

Scott Haneda talklists at newgeo.com
Tue Feb 24 14:35:28 PST 2009

On Feb 24, 2009, at 6:12 AM, Daniel J. Luke wrote:
> On Feb 24, 2009, at 6:43 AM, Scott Haneda wrote:
>> Can someone pass me links or personal data on the history of  
>> apache2 and how the current directory path was decided on.  All the  
>> other ports I have installed, usually end up in bin or var or etc,  
>> but apache2 stands alone.
> It probably installs that way because it's the default layout for  
> apache2.

I have been reading over the suggestions for MacPorts:

A few questions... how come the apacche2 does not warn me of the  
violation, I see the "violate" in the port file, but as far as I can  
tell, there is nothing when installing it to tell me?  I will confirm  
once more on a install, but i am pretty sure I did not see it.

If I modify the port to put apache in www, I believe that to be the  
correct place based on the above url, is this a huge undertaking that  
is going to require a lot of discussion to not break thing?  Every  
path is going to need to change.

To me it is worth it to follow the guidelines of MacPorts, but this  
may be one that is so engrained in MacPorts, it might not want to  

My feeling is, the sooner the better, there are already a handful of  
blogs out there, which instructions and hard paths in their  
instructions pointing to the current location.  The sooner we put it  
where MacPorts recommends, the better the long term usability is going  
to be.

* If you contact me off list replace talklists@ with scott@ *

More information about the macports-users mailing list