OK, After some search, it appears that hg sub repos don't work like svn:externals. They tries to preserve a consistent snapshot of the repositories (both main and nested) and in this case, it's logic to require from developers of the main repo to update the .hgsubstate file.
So currently, the phing script is more useful but when chamilo will be more stable, maybe subrepo will be more suitable. Even if it's not totally related I found this article interesting about how to manage subrepos [1] Goulwen [1]: http://rustyklophaus.com/articles/20100124-SubmodulesAndSubreposDoneRight.html ----------------------------------------------------- Twitter : http://twitter.com/nautilebleu/ Skype : nautilebleu Web : http://nautilebleu.tumblr.com/ 2011/3/11 Hans De Bisschop <hans.de.bissc...@ehb.be>: > Hi Goulwen, > > From memory the "main" repository has an hgtags file which lists all > "curret" states of it's subrepositories. Again, if I remember correctly, if > you pull or update that subrepo, it's only updated to the revision listed in > that hgtags file. To be able to update that hgtags file and the subrepo > state you need write access on the parent repository ... which not everyone > has. So that leaves it up to people with access to everything to constantly > update or monitor those states. Or at least that's how we understood it. > > If you know of some practical examples that show us it's not like that, > please ... PLEASE ... tell us. > > Best regards, > > Hans > > On 11/03/2011 16:31, Nautile Bleu wrote: > > Hi all, > I'm currently updating my copies of the repositories. While the phing script > works well, it's not really easy to see what's have been changed when you > update all repos via php script/phing.php get-all. Especially you need to > parse all the output to find repositories that need to be updated (because > of a extra head caused by a local commit for example) > The doc on Google [1] about the migration explain why splitting the > repository, but it doesn't explain why use a custom script and not Mercurial > subrepositories [2][3] which seems to work the same way, but is a built-in > feature plus allow to push all in one command. It also allows to pull in one > step with pull --update. Plus it supports colors if you had them in your > terminal :) > Regards, > Goulwen > [1] > https://docs.google.com/document/d/1Nfk6DG47Qc76U0zEb9vshdYkalP0aEROr0X6mtJoeYw/edit?hl=en&authkey=CNTNnrYC&pli=1# > [2] http://mercurial.selenic.com/wiki/Subrepository > [3] http://mercurial.aragost.com/kick-start/en/subrepositories/ > ----------------------------------------------------- > Twitter : http://twitter.com/nautilebleu/ > Skype : nautilebleu > Web : http://nautilebleu.tumblr.com/ > > _______________________________________________ > Dev mailing list > Dev@lists.chamilo.org > http://lists.chamilo.org/listinfo/dev > _______________________________________________ Dev mailing list Dev@lists.chamilo.org http://lists.chamilo.org/listinfo/dev
