Hi Ryan, Hi all, > Le 19 janv. 2015 à 11:07, Ryan Schmidt <ryandes...@macports.org> a écrit : > > On Jan 19, 2015, at 3:59 AM, Akim Demaille wrote: >> >> You're talking implementation details, I'm talking feature. And the >> implementation is straightforward: rm -f /opt/local/macports/software/<PORT> >> when <PORT> was activated. > > It's quite a lot more than just that. You're asking for a way for the user to > opt in to auto-removal of archives and opt out of the ability to use the > deactivate feature. MacPorts currently relies on the deactivate feature > during uninstallation, so there would be changes required there as well.
I have a question: what exactly is in the archive? Why is that that deactivate does not archive what was installed on the disk? I mean, if the archives is exactly what is deployed, then it's pure duplication, including in an activate/deactivate scenario: one copy should be enough, be it deployed, or compressed, no? Maybe that would be less invasive, I don't know. Also, do people really use deactivate/activate offline? _______________________________________________ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
