I'm trying to migrate from a CVS to a SVN repository using TortoiseSVN
as a client.
I have the following structure for a project:
The default modules are always there, and should just appear when
checking out 'project'. This works. However, some developers work on
some additional modules, but not every developer should (or wants to)
check out all modules all the time. So what we used to do, is checkout
the module 'customer1' (which is separate in the repository, ie on the
same level as 'mainproject') to the location 'mainproejct > modules >
customer1'. Then, we could just do a cvs update/commit on 'mainproject',
and it would recurse into customer1 as well. I assume this 'just works'
because CVS basically considers each folder a separate entity, and
doesn't really care that I'm mixing folders from different repositories.
I'm trying to do the same with tortoisesvn. I've got the repository urls
svn://svnserver/trunk/mainproject and svn://svnserver/trunk/customer1
I've checked out mainproject, opened the folder 'modules'. Explorer
doesn't offer 'checkout' (probably because it already sees SVN
metadata), so I tried checking out 'customer1' into a temporary
directory, and then moving it back into modules.
Unfortunately, this doesn't do what I want. If I run 'svn update' on
mainproject, it will update 'defaultmodule1' and 'defaultmodule2', but
won't recurse into the separately checked out 'customer1' - I have to
update that one separately. Is there a way to get TortoiseSVN to recurse
into these directories, or should I be setting up my repository differently?
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2009-11-17 11:56:11 CET