Managing Dependencies with Subrepositories - Partial Checkout and Commit/Push Propagation

Mina R Waheeb syncer at gmail.com
Wed Jan 20 16:07:49 CST 2010


What is your question here?

Lets say repo B subrepo of A, clone of A will clone B too.
If you did a modify some files in repo B and modify some files in repo A!
The expected behavior that the modification in repo A depends on the 
modification in repo B. How you wana commit repo A without committing repo B?
Anyway, You still free to commit repo B without committing repo A!

If you have a parent repo used as dummy repo to handle the tags and default 
branch of huge project and you don't wana commit the root repo each time you 
commit something in subrepo of it. you can use the forest extension and use 
fpull command to pull the default branch of all subrepos.

We use HG for managing dependencies and its doing very well :)

Cheers,
Mina R Waheeb

On Wednesday 20 January 2010 5:17:44 pm Michael P. Jung wrote:
> I wonder if nobody else is using subrepositories for managing
> dependencies and got similar problems. I'm really looking forward to
> some less 'clever' subrepositories that don't receive commit and push
> commands from the main repository.
> 
> 
> --mp
> _______________________________________________
> Mercurial mailing list
> Mercurial at selenic.com
> http://selenic.com/mailman/listinfo/mercurial
> 


More information about the Mercurial mailing list