[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Sparse Directories vs Externals

From: void pointer <rcdailey_at_gmail.com>
Date: Sat, 21 Feb 2009 23:45:38 -0600


I'm in a situation where I have an "engine" that several projects depend on.
I want to make each project independent and checkouts shall be performed for
each project. I have 2 ways I can go about this as far as I know:

   1. I can perform a checkout of each project individually and have an
   external link to the "engine". This is very conservative and as far as the
   functional end-result is concerned, this is exactly what I want.
   2. All projects could be "under" the "engine" and I could check out the
   engine and use sparse directories to exclude the projects I am not
   interested in.

In order to do option #2, which is ideal because I like to avoid the use of
externals that point internally to the same repository, I need to have the
ability to explicitly exclude items from my working copy post-checkout. For
example, if I make sure to properly setup my sparse directories on my first
checkout and someone adds a new hefty project later, I'll be forced to get
that project on my next update (At least that is what I feel will happen). I
don't want to have to keep doing fresh checkouts every time I want to
exclude something else. Is there a way to exclude things after a checkout
has already been performed?


To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-02-22 06:47:09 CET

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.