[MacPorts] #15937: port deactivate is a bit blood-thirsty (acts like it would delete /)

[MacPorts]

#15937: port deactivate is a bit blood-thirsty (acts like it would delete /)
---------------------------------+------------------------------------------
  Reporter:  stephen at xemacs.org  |       Owner:  macports-tickets at lists.macosforge.org
      Type:  defect              |      Status:  closed                               
  Priority:  Normal              |   Milestone:  MacPorts base bugs                   
 Component:  base                |     Version:  1.7.0                                
Resolution:  wontfix             |    Keywords:                                       
---------------------------------+------------------------------------------
Changes (by raimue at macports.org):

  * status:  new => closed
  * resolution:  => wontfix

Comment:

 Replying to [comment:4 ryandesign at macports.org]:
 > Actually I wouldn't even change that. A port might install a directory
 in, say, /Applications/MacPorts. For example for minivmac 3 I want to make
 a directory /Applications/MacPorts/Mini vMac. And lesstif installs a
 directory in ${x11prefix}/LessTif. MacPorts should remove these
 directories if these ports are uninstalled.

 /Applications/MacPorts is in our mtree, ${x11prefix} is not. So lesstif
 would not get uninstalled correctly if we would change that. Also there
 would be no automatic cleanup if a port accidentally installs files
 outside the mtree.

 > So since I haven't heard of any detriment being caused by the code the
 way it is, and changing it will cause problems as detailed above, I would
 say we should close this as wontfix.

 I agree. Closing as wontfix.

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