port selfupdate is not appropriate anymore simply because it will
overwrite your self-built copy of macports with the latest released
version (well, it actually won't do this until the latest released
version is a higher version number than what you currently have
installed). I mean, if that's what you want, go ahead and do it, but
if you'd rather stay pegged to the tip of trunk, you need to do svn
update/make/make install yourself. And yes, that svn checkout command
got the latest source that the developers are working from, and svn
update, when called in the directory produced by the checkout, does
just "know" where the repo is and updates from it.
-Kevin Ballard
On Jan 7, 2008, at 9:41 AM, Chris Janton wrote:
So at what point should
port selfupdate
work on 10.3.9 systems again?
It's not clear to me, but I assume that this command
svn checkout http://svn.macosforge.org/repository/macports/trunk/base
gets the "real thing" - the current port sourcecode, and that the
update that was obtained by this command
svn update
(svn "knows" where the source repository is, etc. etc.)
--
Kevin Ballard
http://kevin.sb.org
[EMAIL PROTECTED]
http://www.tildesoft.com
_______________________________________________
macports-users mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo/macports-users
