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

Re: Nested Subversion Checkout

From: Olivier Dagenais <olivier.dagenais_at_formark.com>
Date: 2007-05-15 00:45:12 CEST

> The problem is that we have many different sites and some parts of the
> site run common "software" such as a members area that is standard for
> each
> site except for layout changes and so on. So what I need to do is checkout
> the sites code, that is no problem. But then the structure of that site
> would have a web directory and in that directory there would be another
> called members. Now into that directory I would need to checkout another
> repository, that contains our members software. Now I have just been
> testing
> on my local machine using TortoiseSVN and it seems I can not checkout
> another project into that directory.

I see what you're trying to do, but I would do it differently: I would
commit a copy of the "standard" bits to each site's repository, with a note
in the commit comment (and/or a subversion folder property?) as to which
revision of the standard bits have been updated. That makes the sites'
make-up less of a moving target and more predictable because you need only
ask for code from one repository when it's time to test a site. It also
means fixes done in that "branch" will need to be propagated into the
authoritative repository on occasion, but it does make it such that those
hypothetical "fixes" (ok, "hacks") for one site won't risk jeopardizing
other sites.

That's the approach we use when we have projects use a common class library.
Since your "standard" software may consist of many more files than a class
library and its associated documentation, you may choose to commit a ZIP
file that contains all files and have your build script unzip it into the
appropriate folder when compiling. Your "pull" updates would be easier this
way, but your repository might grow in size faster as a result and private
changes will be incredibly difficult.

> Will I have to check them outside the site area and then copy them
> manually?

If anything, you'll end up writing a batch file that performs a checkout of
one repository and an export of another.

> And is there a way to get rid of the .svn folders in a working copy so
> that
> they do not end up on a site?

That would be an "export", which asks Subversion for "an unversioned copy of
a tree"; in other words just the files in the repository and none of the
"control folders" (.svn).

Olivier Dagenais
Software Engineering / Génie logiciel
Formark - Combine the Best of SharePoint® and Livelink®
Phone: 613-599-5173 ext 238
Make sure you don't miss anything: subscribe to the Formark Newsletter:

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue May 15 00:45:45 2007

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.