-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Monday 28 October 2002 13:07, Karl Fogel wrote:
> Great! You're the first case (that I know of, anyway) of using
> svn:externals in real life.
Just to get in my two cents, I use svn:externals to manage my home directory.
My entire ~/ is a working copy, and instead of running "svn co" to check out
other working copies, I set svn:externals.
One problem I just noticed recently: maybe this is intentional, but it's
annoying. While svn checkout and update traverse svn:externals just fine,
svn status (and possibly other commands, I haven't fully checked) treat the
external directories as non-versioned.
$ REPOS_1=$PWD/test-repos-1
$ REPOS_2=$PWD/test-repos-2
$ svnadmin create $REPOS_1
$ svnadmin create $REPOS_2
$ REPOS_1=file://$REPOS_1
$ REPOS_2=file://$REPOS_2
$ svn co $REPOS_1 test-wc
Checked out revision 0.
$ cd test-wc
$ svn pset svn:externals "foo $REPOS_2" .
property `svn:externals' set on ''
$ svn ci -m ""
Sending .
Committed revision 1.
svn $ svn up
At revision 1.
$ ls
## This is another problem: why do I have to clear the wc
## before svn:externals will be honored?
$ cd ..
$ rm -rf test-wc
$ svn co $REPOS_1 test-wc
Checked out revision 1.
Fetching external item into test-wc/foo
Checked out revision 0.
$ cd test-wc
$ svn st
? foo
^^^^^^^^^^ Here is the problem. Status should descend into external
directories just like update does, and should not print anything if the
external dirs have no changes.
- --
Peter Davis
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)
iD8DBQE9vcDQhDAgUT1yirARAq26AJ4/ijsz8szn8IqM7X2Bk7cTgxjpGgCePrSQ
4C82ZHtTm+dGp2R8p2iWji4=
=8WvC
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Oct 28 23:58:16 2002