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

Re: Multiple Projects, One Working Directory

From: Ryan Schmidt <subversion-2006c_at_ryandesign.com>
Date: 2006-08-08 20:01:14 CEST

On Aug 8, 2006, at 18:50, Rob Wilkerson wrote:

> I have a repository that contains multiple projects. Each project has
> its own branches-tags-trunk structure, but I need to be able to check
> out the contents of each project to the same working directory. There
> is one core project and the other projects are "addon modules" that
> work within the core context. The reason for keeping them separate is
> that we build, sell, package and ship them separately.
> Core and addons both install from the product root directory. Is it
> possible to checkout files from multiple projects to the same working
> directory using TortoiseSVN (or any other client, I assume)?
> If you're wondering how/why they both checkout to the same working
> directory, each addon contains a few files that are web accessible and
> a few that are not. There are directories allocated in core to hold
> these, but in order to access them from one install root, I need to
> mirror the core path in the addon repository so the files end up in
> the right place. Hopefully that explains just a little. It's not
> ideal, but it's the hand I was dealt.

No, that's not available. You can have working copies inside other
working copies, but you cannot check out two repository paths to the
same local directory.

So, for example, you could easily have:

project/ <-- working copy of project
                foo/ <-- working copy of foo plugin
                bar/ <-- working copy of bar plugin

And you could even automate the creation of such a nested working
copy using svn:externals. But I don't think there's a way to do what
you're asking.

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Aug 8 20:02:57 2006

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.