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

MacPorts noreply at macports.org
Mon Nov 10 17:33:20 PST 2008


#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:                     
--------------------------------+-------------------------------------------

Comment(by talklists at newgeo.com):

 So far, it does not look like anyone is offering up suggestions on how to
 solve this, other than jmr@, perhaps I can help.  As with most other
 config file software, you do not touch the config files.  in apache's
 case, anything that ends in .conf, and further, anything that was added
 and is not a part of the initial install, needs to be left untouched.

 Apache is pretty nice in that config files are in well known places, so it
 should be simple to leave them alone.  Every now and then, even Apple will
 write over your *.conf files, and cause trouble, but it has been at least
 a year since this last happened.

 The solution as I see it is that upgrades do not touch *.conf files,
 period.  Major version updates will need to be taken into consideration.
 As far as I can remember, the config file options do not change over
 time/versions.  So while the 1.3 branch has it's config file, and the 2.x
 branch certainly was changed, within major versions, they do not change.

 Since version 1 and version 2 install in totally different locations, this
 still remains a non issue.  In the rare event that a apache update adds
 and/or changes functionality to a config file, the port maintainer needs
 to provide a patch that will change the files in place.  Ideally, making a
 backup as well.  More ideal, in my opinion, is to simply provide a patch
 script and let the user run it locally.  If files are to be edited in
 place, make a backup, and stuff a note in it as to why it exists.

 I am a bit paranoid about this, so I move my config files for most
 everything, like named.conf and httpd.conf and many others, elsewhere.
 This is not in MacPorts, but in plain OS X that I do this.  I then simply
 link from the standard location, to the new location.  If an update wipes
 a link, no big deal, I can diff the files, and repair.  I am yet to run a
 diff that found a diff, for some reason Apple just likes to replace config
 files for no reason.  Probably easier than excluding them.

 OS X Server more or less does not touch your config files, or they update
 the old ones, to match the new ones, without altering your settings.  This
 can, and has caused issues, but a careful `awk` can usually do just fine.

 Comments?

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


More information about the macports-tickets mailing list