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

Re: How can a project be divided up between two repositories?

From: Les Mikesell <lesmikesell_at_gmail.com>
Date: Thu, 15 Oct 2009 13:02:00 -0500

Ryan Schmidt wrote:
> On Oct 15, 2009, at 02:43, Tom Lenz wrote:
>> Suppose I have two sets of files that I want under version control,
>> Site
>> A and Site B, containing files as follows:
>> Site A:
>> File_a
>> File_b
>> File_c
>> File_d
>> Site B:
>> File_e
>> File_b
>> File_c
>> File_d
>> I want to find a way to specify:
>> If a change is made to File_a, it applies only to Site A. Call this
>> Group 1.
>> If a change is made to File_e, it applies only to Site B. Call this
>> Group 2.
>> If a change is made to File_b, File_c or File_d, the change gets
>> applied
>> to both Site A and Site B. Call this Group 3.
>> The files have to be in a certain location relative to a directory
>> structure. For example, File_a and File_e must be in the same
>> directory.
>> Also, in some cases, File_a and File_e have the same name.
>> From time to time it may turn out that I want to move a particular
>> file
>> from Group 3 to Group 1 or Group 2.
>> The way we're doing it now is that Site A is in one repository and
>> Site
>> B is in another repository, which works and is sort of simple, but it
>> has a big disadvantage in that if files in Group 3 get changed, they
>> must be manually copied to from one site to another. This is a little
>> worse in our case because in reality there are more than two sites
>> involved.
> I would suggest putting everything in one repository. Create a
> directory Site A containing the files unique to site A, a directory
> Site B containing the files unique to site B, and a directory Global
> containing the files common to all sites. Use file-level svn:externals
> to bring the common files into each of the sites' directories.

It's not clear what the actual use case is here. For many things that
require localized differences, one approach is to exclude the actual
differing file(s), but include a template with a manual or scripted
approach to generate the variations you need after the checkout.

   Les Mikesell
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-10-15 20:03:09 CEST

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