[MacPorts] #23445: subversion seems to assume apache is already installed - build error for missing programs

[MacPorts]

#23445: subversion seems to assume apache is already installed - build error for
missing programs
----------------------------+-----------------------------------------------
  Reporter:  clemc@…        |       Owner:  macports-tickets@…                   
      Type:  defect         |      Status:  closed                               
  Priority:  Normal         |   Milestone:                                       
 Component:  ports          |     Version:  1.8.2                                
Resolution:  invalid        |    Keywords:                                       
      Port:  subversion     |  
----------------------------+-----------------------------------------------

Comment(by clemc@…):

 JMR:

 I appreciate your time for answering and thank you for the info on
 switches and full path. While I'm new to the MacPorts way, I'm hardly a
 newbie to either UNIX or MacOS X [35 year UNIX guy] etc....
 I have been using fink for years and was recently urged by my OS friends
 at Apple to look at MacPorts.  So for this new machine, I'm trying to set
 up my environment using ports not fink.

 Please note: the error reported by porticus tells the user use the full
 path for the debug log - so I admit I'm a tad confused.

 Also when which "variants" should be checked in Porticus (and ports in
 general) is easy.  I'll not be adding the +darwinXX stuff again if indeed
 it is not needed.

 jmr>>Yes, the mac_os_x_server_mod_dav_svn variant does assume that apache2
 is already present.  ....
 Sorry for my miss-speak, the issue is that if its required, it's not
 finding it.  This seems to be a path expectation issue.

 As I said, in my comments I added that that issue seems to be that the one
 of the tools is assuming /opt/apache2, while port is installing apache2 in
 /opt/local/apache2

 So there seems to be a consistency issue... for a new MacPort users,
 starting fresh, I suspect others will trip over this also....
 and I wonder if I just trip over something that might cause a less
 experienced person to get stuck.  As I said, I solved it with a symlink
 work around, and then filed the bug report

 Thanks again,
 Clem

-- 
Ticket URL: <http://trac.macports.org/ticket/23445#comment:5>
MacPorts <http://www.macports.org/>
Ports system for Mac OS