> I understood that when using base "port selfupdate" did not compile a new > base so I have been in the habit of using "svn up" and manually compiling > base. Should I be running selfupdate for other reasons? > > If so, when? After or before each base install or dports update?
If you're running trunk, selfupdate won't do more than inform you there's no updates (since you're using a newer version) and then sync portfiles. You can effectively just run `port sync` if you're always going to manually run up/make/install of the base code. However, if you do rely on selfupdate to update MacPorts, it sounds like you have to run it twice each time there's an update: once to rebuild the base code and once to then sync portfiles. _______________________________________________ macports-dev mailing list [email protected] http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
