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?
I agree. It also happens that for (some reason) MacPorts decides to upgrade a dependency with another variant. Had that today on a remote VM which apparently had a borked doxygen install, and which insisted on installing doxygen+docs because that variant exists and the dependent port was requested with that variant. I still don't understand, but finally a `upgrade --force` to reinstall the regular version solved the issue. 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 ... R > > Thank you, > Mojca > > *** Yes, I know that in theory I would have to run "port upgrade > outdated" first, but in cases when: > - that would take days or hours to finish (yes, recompiling clang on > an old ppc notebook really takes something in the order of magnitude > of a day) > - the binary package is available, but I'm stuck with "old" variants > that I want to get rid of first to avoid compiling from source > I really prefer to pick the order of updates manually. > _______________________________________________ > macports-dev mailing list > [email protected] > https://lists.macosforge.org/mailman/listinfo/macports-dev _______________________________________________ macports-dev mailing list [email protected] https://lists.macosforge.org/mailman/listinfo/macports-dev
