How do people manage changes to common library files stored across mutiple (Mercurial) repositories?

Question

This is perhaps not a question unique to Mercurial, but that\'s the SCM that I\'ve been using most lately.

I work on multiple projects and tend to copy source code f

Answer 1

use the transplant extension

Answer 2

I'd recommend against your "copy the sourcecode" practice but use binary distribution for your custom libraries instead. These binaries are checked in along the sourcecode.

• reduces build-time
• no overhead of tracking changes in all copies of the library
• you can use different versions of the same library in different projects.

EDIT: And for the issue with "common" or "toolbox" libaries in general, read this post from ayende.

Answer 3

Three solutions, pick your favorite:

1. Put all projects into one repository.
2. Make a separate repository for shared code and different repository for each project.
3. One repository with Subrepositories: https://www.mercurial-scm.org/wiki/subrepos, keep all common code in one subrepo and different subrepos for each project.

Copying actual files between repositories with no common ancestors will never be optimal as history is not preserved.