Re: Help with svn:externals

Paul Lussier <pll@lanminds.com> writes:
> I think so, but it doesn't *have* to external o project A, right?
> For instance, using the homedir example, I could have a repository
> for my home directory:
>
> /path/to/repos/pll
>
> Then within the "project" pll, I could have sub dirs:
>
> /bin
> /etc
> /.emacs
> /Mail
>
> I could then apply an svn:externals tag to each one I could then
> checkout just my ~/bin directory or just my ~/etc directory ?

I'm not sure what you mean, but maybe this will clear things up:

The svn:externals property does *not* live on the externals themselves
(bin, etc, .emacs, and Mail in the above example). It lives on the
directory into which you want them to be checked out (pll, I guess).
The value of the property is a description of what you want checked
out into pll.

Also, only subdirectories work right now, so you can't list .emacs in
that description, unfortunately. Sorry about that.

(Is there some reason you don't just put your home dir under
Subversion directly?)

> I think I'm getting it. I read the CVS modules section, and that
> seemed pretty straightforward. So, is there an equivalent of a CVS
> modules file, or, do I use 'svn propset' to manage the "svn:externals'
> properties of a repository?

It's not very much like CVS modules. I would stay away from CVS
modules docs if you're trying to understand svn:externals. :-)

You use 'svn propset' or better yet 'svn propedit'.

-K

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Oct 22 18:36:03 2002