On May 10, 2007, at 7:44 AM, Vincent Lefevre wrote:
It seems that selfupdate got broken:
prunille:~> sudo port -d selfupdate
DEBUG: Rebuilding the MacPorts base system if needed.
Synchronizing from file:///Users/vinc17/wd/macosx/dports
DEBUG: /opt/local/bin/svn update --non-interactive "/Users/vinc17/
wd/macosx/dports"
It shouldn't update *my* SVN working copy. It was previously updating
the standard path (?) with rsync. I suppose that it takes the paths
from /opt/local/etc/ports/sources.conf, which contains here:
file:///Users/vinc17/wd/macosx/dports
file:///Users/vinc17/software/dports
rsync://rsync.macports.org/dpupdate/dports
But I use this for port installation only.
As Ryan points out, this was a change in 1.4.40. Clearly whoever made
the change did not anticipate the problem you're having with it. We'd
love to hear your suggestions for what the proper behavior should be
in this case. What if the behavior was:
- Update the first sources.conf directory found that either (1) is
an rsync url, or (2) is a valid svn repository.
Would that rule fix things for you?
James
--
Vincent Lefèvre <[EMAIL PROTECTED]> - Web: <http://www.vinc17.org/>
100% accessible validated (X)HTML - Blog: <http://www.vinc17.org/
blog/>
Work: CR INRIA - computer arithmetic / Arenaire project (LIP, ENS-
Lyon)
_______________________________________________
macports-dev mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo/macports-dev
_______________________________________________
macports-dev mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo/macports-dev
