#15937: port deactivate is a bit blood-thirsty (acts like it would delete /) ---------------------------------+------------------------------------------ Reporter: stephen@xemacs.org | Owner: macports-tickets@lists.macosforge.org Type: defect | Status: new Priority: Normal | Milestone: MacPorts base bugs Component: base | Version: 1.7.0 Resolution: | Keywords: ---------------------------------+------------------------------------------ Comment (by ryandesign@macports.org): Replying to [comment:3 raimue@macports.org]:
I did not look at the code yet, but we do not prevent files being installed anywhere outside the prefix. port only issues a warning if this happens.
Also, some files reside intentionally in `/Applications` and `/Library`, so I assume stopping at ${prefix} would not deactivate them correctly.
You're right about that. We should not stop at ${prefix} as I pondered earlier. So we shouldn't change anything there.
I would say port deactivate should only prune empty directories if it is in our mtree.
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. 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. -- Ticket URL: <http://trac.macports.org/ticket/15937#comment:4> MacPorts <http://www.macports.org/> Ports system for Mac OS