[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: Rob Wilkerson <r.d.wilkerson_at_gmail.com>
Date: 2006-08-09 14:14:14 CEST

Hey Simon -

The docs are back up this morning so I took a look and I think that
maybe, just maybe, svn:externals may offer some promise. I'd like to
explain my situation, though, to determine whether it will work:

I have a core code base...

installroot
   /dir1
   /dir2
   /mod
      /addons
      /core
   /shared
      /images

In my scenario, each addon module is a separate project within the
same repository as core. Each addon lives in its own folder so I
could, from the installroot, define an external project for each addon
as:

mod/addons/addon1 http://www.myproject.com/repos/project/addons/addon1/trunk
mod/addons/addon2 http://www.myproject.com/repos/project/addons/addon2/trunk

If I understand this correctly, that doesn't appear to be any problem.
 Here's where it might be dicey...

That addon project also contains images that need to be checked out to
/shared/images, but here's the catch: that directory *also* contains
images populated by the core project. Can svn:externals handle a
directory that is populated by multiple projects?

I appreciate your insight on this. I'm just undergoing the transition
from VSS and I don't want to handicap myself before I ever get
started.

On 8/8/06, Simon Large <simon@skirridsystems.co.uk> wrote:
> Rob Wilkerson wrote:
> > I'm honestly not sure whether this is the proper forum for my
> > question, but I thought I'd try this first and then move on to the
> > Subversion mailing list if it's a better fit.
> >
> > 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.
>
> I would point you to the online docs but they don't seem to work at the
> moment. Look in the help file at Appendix B "How Do I ...", section 6
> "Include a common sub-project".
>
> Simon
>
> --
> ___
> oo // \\ "De Chelonian Mobile"
> (_,\/ \_/ \ TortoiseSVN
> \ \_/_\_/> The coolest Interface to (Sub)Version Control
> /_/ \_\ http://tortoisesvn.tigris.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tortoisesvn.tigris.org
> For additional commands, e-mail: users-help@tortoisesvn.tigris.org
>
>

-- 
Rob Wilkerson
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: users-help@tortoisesvn.tigris.org
Received on Wed Aug 9 14:14:24 2006

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