[MacPorts] #32190: couchdb 1.1.1 preserve local.ini between installs

[MacPorts]

#32190: couchdb 1.1.1 preserve local.ini between installs
----------------------------------+-----------------------------------------
 Reporter:  erik@…                |       Owner:  macports-tickets@…                   
     Type:  defect                |      Status:  new                                  
 Priority:  Normal                |   Milestone:                                       
Component:  ports                 |     Version:  2.0.3                                
 Keywords:                        |        Port:                                       
----------------------------------+-----------------------------------------
 I would argue that the local.ini, or at least a modified local.ini, should
 be left alone by uninstall and install. As it stands, the local.ini is
 removed by uninstall, and install will fail at the activation stage if a
 (modified?) local.ini already exists.

 The use case is an uninstall / install.

 I think preservation of local.ini would be expected behavior, and that a
 warning, but not error, during installation of an existing local.ini is
 merited.

 After all, the couchdb database is left alone during uninstall / install,
 as one would expect. However, wiping the local.ini can effectively disable
 the database.

 I might mention that a common tactic to deal with a broken install is to
 uninstall/install a port, and finding your local.ini wiped is unpleasant.

 according to the couchdb docs and the comments in local.ini the local.ini
 is not supposed to be touched by a "server upgrade" . I think this policy
 can be fairly extended to this case.

-- 
Ticket URL: <https://trac.macports.org/ticket/32190>
MacPorts <http://www.macports.org/>
Ports system for Mac OS