[MacPorts] #8605: BUG: apache2 doesn't leave modified extra config files alone

[MacPorts]

#8605: BUG: apache2 doesn't leave modified extra config files alone
--------------------------------+-------------------------------------------
  Reporter:  wyuenho at gmail.com  |       Owner:  imajes at macports.org
      Type:  defect             |      Status:  new                
  Priority:  Normal             |   Milestone:  Port Bugs          
 Component:  ports              |     Version:                     
Resolution:                     |    Keywords:                     
      Port:  apache2, apache20  |  
--------------------------------+-------------------------------------------
Changes (by ryandesign at macports.org):

  * port:  => apache2, apache20


Comment:

 There's nothing particularly complicated here to do or explain, it's just
 nobody has done it yet. The apache2 port already does not overwrite your
 httpd.conf; now it just needs to also not overwrite your extra conf files.

 I don't think it's reasonable to expect MacPorts to upgrade your non-
 MacPorts-managed conf files though. I wouldn't expect the maintainer to
 provide an upgrade script either. It is the user's responsibility to
 inspect the new sample conf files for any changes, and apply them to their
 own conf file. Or you could suggest to upstream that they should develop
 and supply an update script with apache2, which the MacPorts port would
 then of course also provide as soon as it's updated.

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