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

RE: Multi-modules / subdirectories

From: <webpost_at_tigris.org>
Date: Mon, 16 Mar 2009 02:34:21 -0700 (PDT)

Thank you for your suggestion.
I tried to do something with externals before, but since it just copied a directory with the properties on it, I thought that externals was not the right way to go.
However I did not know about svncopy.pl. I will check what it does exactly.

A couple of questions about this, if you don't mind.

The svn:externals are set on the Project1 and Project2 directories?

Are there any plans to integrate the functionality of svncopy.pl in TortoiseSVN or Subversion itself?

Is there a windows tool to do this, instead of having to use perl?

Thanks.
Robert

> How about something like this:
>
> /trunk
> /Module1
> /Module2
> /SharedModule
> /Project1
> /Module1 (external)
> /SharedModule (external)
> /Project2
> /Module2 (external)
> /SharedModule (external)
> /tags
> /Project1-1.0
> /Module1 (external_at_350)
> /SharedModule (external_at_350)
> /Project2-1.0
> /Module2
> /SharedModule
> /branches
> /Project1-1.0-updates
> /Module1
> /SharedModule
> /Project2-1.0-updates
> /Module2
> /SharedModule
>
> Now, when you tag Project1 you can use svncopy.pl and it will pin the
> externals in the tag to the current revision of module1 and shared
> module.
>
> BOb
>
>

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=1332241

To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-03-16 16:01:40 CET

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.