On May 18, 2010, at 2:10 PM, Bradley Giesbrecht wrote:
> So if I have svn checkout in sources.conf and I do "port selfupdate" my
> changes to <prefix>/var/macports/sources/svn.macports.org/trunk/dports won't
> be clobbered?
> I didn't know that. How would I change back to the macports files later?
It'll run a 'svn update' on your dports dir (I tend to run svn update manually,
so I don't end up running 'port sync' or 'port selfupdate' that often). You
could end up with a conflict (if you change a file that gets changed by someone
else) - and you'll have to deal with that (the subversion documentation has a
pretty good description of what's involved).
You use subversion to manage your changes then, so you could do a 'svn revert'
to revert your local changes.
> I believe I was following the suggestion at the end of "port selfupdate" to
> do "port upgrade outdated".
>
> So are you saying if I do "port upgrade x" and port x depends on port "y" and
> port "y" is outdated then port will not upgrade port "y".
No, I'm saying that port does what you tell it to.
'port upgrade' follows dependencies (and upgrades them), because that's what
almost everyone would expect to have happen. If you don't want that behavior,
it's simple enough to add '-n' to the port command you're going to run (it's
even documented in the man page).
--
Daniel J. Luke
+========================================================+
| *---------------- dl...@geeklair.net ----------------* |
| *-------------- http://www.geeklair.net -------------* |
+========================================================+
| Opinions expressed are mine and do not necessarily |
| reflect the opinions of my employer. |
+========================================================+
_______________________________________________
macports-dev mailing list
macports-dev@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
