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

> 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.

> 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.

> IMHO the above requirements are contrary to subversion centralized
> approach.
> You could try a distributed version control system like git or bazaar
>

> Have you considered using one repository and using the
> --depth/--set-depth options to control which files are visible in work
> spaces for each group of users?
>
Thanks to everyone for the helpful suggestions and info. git looks pretty interesting, my boss most likely wouldn't go for it. This svn:externals seems like it will do just what I was looking for.

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

To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-10-16 15:11:32 CEST