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

Re: Sparse Directories vs Externals

From: Ryan Schmidt <subversion-2009a_at_ryandesign.com>
Date: Sun, 22 Feb 2009 02:04:19 -0600

On Feb 21, 2009, at 23:45, void pointer wrote:

> 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:
> 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.
> 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,
> [snip]

Out of curiosity, why do you want to avoid externals that point to
the same repository? It works fine. Especially with Subversion 1.5's
new relative externals.


To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-02-22 09:05:37 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.