pll@lanminds.com writes:
> After reading the svn Handbook section on the svn:externals property
> tag, I find that I'm still a little confused on what it is good for
> and how it is used.
They're a way of causing a checkout of directory A to trigger
checkouts of "external" directories A/X, A/Y, etc, where "external"
means that X and Y might come from a different repository than A. The
value of the svn:externals property specifies exactly where X and Y
come from.
Once X and Y are checked out into A, they will be updated whenever you
run 'svn update' from inside or above them.
So if you have a project A that depends on some other project X in
another repository, you could use svn:externals to check out a working
copy of X *inside* your working copy of A every time.
Does that help?
-K
> I recently read an article in Linux Journal about someone who kept
> their entire homedir under CVS control and used CVS modules to make
> it a bit more manageable.
>
> svn:externals *seems* to be the analgous to CVS modules. However,
> I know very little about CVS at that level, having simply used it to
> check out from repos managed by others. As a result, since I don't
> even understand that, I find it difficult to grasp the svn:externals
> stuff as well.
>
> Could someone be so kind as to explain how/why you would use
> svn:externals? If other docs exist explaining it differently
> than the Handbook, pointers to those would be greatly appreciated as
> well (would it be worth reading the modules section at red bean?).
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Oct 22 17:33:59 2002