On Sun, Feb 15, 2015 at 1:54 PM, Carlo Tambuatco <[email protected]> wrote:
> Seems like macports should have an option that prunes this stuff after > every upgrade. It should be the port developer's responsibility to mark > what is needed to run their port and have the rest deleted after every > upgrade. I would not like this at all; why reinstall the same 10 or so (that "or so" can be quite large for gtk-based ports) build dependency ports every time I install some other port? -- brandon s allbery kf8nh sine nomine associates [email protected] [email protected] unix, openafs, kerberos, infrastructure, xmonad http://sinenomine.net
_______________________________________________ macports-users mailing list [email protected] https://lists.macosforge.org/mailman/listinfo/macports-users
