On Feb 18, 2014, at 16:35, Clemens Lang wrote: > > later on when mixing this port with binaries built by our buildbot which > expect the newer dependency version. So, in summary, don't use -p unless > everything you do is download stuff (which is really the only reason why it's > there in the first place).
Hmmm, you've got a point. Don't think I ever ran into it but I'll remember (off late on 10.6 it was too tempting to use -p). > You might be able to get around re-installing MacPorts itself by running sudo > port -f selfupdate, which will make sure your version of MacPorts base is > built on Mavericks and for Mavericks. > ... > Safe yourself some trouble and follow migration. If you'd like to automate > the process use the script from the "Automatically reinstall ports" ports > paragraph at http://trac.macports.org/wiki/Migration#automatic. Things started out fine, but somehow I found myself with a 64bit-only libiconv (despite the fact that the database told me I had the universal variant, as requested), which of course gave problems. Couldn't figure out how to force-reinstall the port, so I uninstalled it, and then of course gnutar no longer worked. Long story short, I'm following the migration guide now. I presume the tcl "restore" script restores all ports in the input list, and not only the most recent versions of the listed ports, so I'd have to uninstall all inactive ports before generating the list if I don't want to have to prune it by hand? R. _______________________________________________ macports-users mailing list [email protected] https://lists.macosforge.org/mailman/listinfo/macports-users
