Chained cloning of subrepos

[Martin Geisler]

Edouard Gomez <ed.gomez at free.fr> writes:

> Le Tue, 20 Jul 2010 18:29:12 +0200, Didly Bom wrote :
>> In our company we use relative paths when defining subrepos
>> extensivelly. In particular we use relative paths which refer to
>> folders outside of the top folder of the repository (e.g. "../lib" as
>> in Martin's example).
>>
>> While we know that this has the limitation that you cannot chain
>> clones it allows us the flexibility of changing the root folder that
>> contains all our repositories in our central repository "server" to a
>> different folder or even to a different server.
>
> That is exactly the case in my company too, where the build system was
> replicated a gazillion times over the numerous subprojects. I
> concluded exactly like you, having the oportunity to change the root
> was way more important than being able to chain clone subrepos. So my
> coworkers and I took the habit to not clone a project but clone the
> repo layout.

Interesting, thanks for the input.

>> Note that this was before there was any talk about adding a method to
>> create aliases for the subrepository sources (as is being discussed
>> now in the mailing list).
>
> I didn't know about this new planned feature, this could indeed help a
> lot. If aliases can be overriden locally, that could solve it all.

Truth to be told, the feature was only planned a week or two ago when a
company contacted me and asked for it... So you couldn't have known! :-)

Since you and Didly are using subrepos heavily in production, I need all
the ideas I can get from the two of you. So please read as much of the
discussion that you can find time for... I'll try to post a summary
later, hopefully later today.

-- 
Martin Geisler

aragost Trifork
Professional Mercurial support
http://aragost.com/mercurial/