Updating ports tree
There are other tools for doing upgrades, and several (including First, figure out if any packages need to be upgraded manually. You can do this one of two ways: either do a fully automatic upgrade, or do the upgrade bit-by-bit.There isn't really any good way of doing this that I've figured out, but I've made a list of packages I've had problems with below. The latter is STRONGLY recommended, as it allows you to go slowly and test things.This means that changes checked in from the working copy will add new revisions on that branch, while leaving the main trunk and other branches unaffected.To find out what branch a working copy is on, you can use the `status' command.And similarly to a regular `update' command, `update -r' merges any changes you have made, notifying you of conflicts where they occur.Once you have a working copy tied to a particular branch, it remains there until you tell it otherwise.The fully automatic upgrade will break things, and may take a lot of time to fix.* WARNING: If you have a lot of ports installed (who doesn't?
Instead of the main Mac Ports mirror (which is sponsored by Mac OSForge, which is run by Apple, which is thus bound to US law and export restrictions to Iran), you can use an alternate rsync mirror from the list at
Seems clear enough to me : ""If you are following the 6.2 -stable branch:"" Or what ever branch you are following.