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

Re: Recursive commit/update when checking out projects inside projects

From: Andy Levy <andy.levy_at_gmail.com>
Date: Tue, 17 Nov 2009 06:35:01 -0500

On Tue, Nov 17, 2009 at 05:54, Arnold Hendriks <a.hendriks_at_b-lex.nl> wrote:
> Dear list,
>
> 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:
> mainproject
> +- modules
>    +- defaultmodule1
>    +- defaultmodule2
>
> 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?

It doesn't do what you want because it's not the right way to do it.
You can't put things into a working copy without telling the working
copy.

What you really want is svn:externals.
http://svnbook.red-bean.com/en/1.5/svn.advanced.externals.html
http://tortoisesvn.net/docs/release/TortoiseSVN_en/tsvn-dug-externals.html

------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=2418888

To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2009-11-17 12:35:09 CET

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.