CODEWITHSUNDEEP
mercurial
Paul W Homer
Paul W Homer

Reputation: 2750

How to work with overlapping repositories in Mercurial

Often I want to have a main repository of source, shared by several "similar" projects. Each sub-project contains most of the same files, but is a specific configurable instance. That means there are usually a bunch of files and directories that need to be different for each instance.

In CVS I used to create the main repository and the secondary ones, then use the modules file to bind the two together for a specific name. In SVN I used svn:externals to tie back the secondary directories into the main one.

What works in Mercurial?

Upvotes: 3

Views: 311

Answers (1)

VonC
VonC

Reputation: 1328712

It depends on the nature of the specific files that need to be different.
If you can transform them as template files, then you can:

  • have a main repo shared as a SubRepo (as said in the documentation: SubRepos are the "closest to what you can achieve with Subversion directories marked with the svn:externals property")
  • have "similar" projects which will:
    • include that main repo as a subrepo (referencing a specific revision)
    • run a versioned script which will take those template files and build the actual files with the right values per environment.

That way you keep separate the templates (in the main repo) and the values (which each similar projects know about depending on their specific environment).
That being said, not every variation of files can be processed as "templates to be instantiated".

Upvotes: 4

Related Questions