On Thu, Feb 19, 2015 at 1:33 PM, René J.V. wrote: > On Thursday February 19 2015 11:58:46 Mojca Miklavec wrote: > >> That sometimes really annoys me. Is this additional piece of >> information easy to print in advance or does it require dirty >> hacks/lots of code? > > Mojca: I've grown the habit to use -n almost all the time to avoid > unasked-for upgrading ... but as shown above that doesn't always prevent all > upgrading ...
I admit that I didn't think of doing that, but even if I was, I could never be sure if that is "safe enough". When I don't know what changes were done, there's always a risk that I'll end up with a broken port. (I don't want to recompile clang just because I thought that recompiling a tiny dependency wasn't important enough. Or deal with hard-to-debug problems just because I would first recompile the master port, then the dependency, and the dependent port would no longer work properly afterwards.) Mojca _______________________________________________ macports-dev mailing list [email protected] https://lists.macosforge.org/mailman/listinfo/macports-dev
