Mercurial and library repos

[Gregory Allen]

I have a "libraries" repo and several different project repos. Each  
project needs files from the libraries. Using Subversion's  
svn:externals, you can make your project repo refer to a certain  
version of an external repository.

I can't be the first person to have this problem, and I've seen this  
questions asked before. Sometimes the answer is:

> This is really not what hg was made for, so you should try a  
> different way of working.

:) What is the way I should be working?

I've seen ForestExtension suggested, but the API is ... complex. A new  
set of commands depending on where you are in the tree is likely to  
cause confusion and error.

I've also considered cloning the libraries repo to make a new project.  
Then I could use MQ to maintain patches to the libraries, that could  
get reapplied back up to the mainline libraries repo. Again, two sets  
of APIs that makes it complex for the user.


What is the workflow to solve this problem that the Mercurial gurus  
would use?

I'm trying to advocate Mercurial, but this is a sticking point.

Thanks,
-Greg

Gregory E. Allen, MSEE Engineering Scientist
Applied Research Laboratories: The University of Texas at Austin
Please help find my missing daughter: http://FindSabrina.org/