28 Jun
2014
28 Jun
'14
5:22 a.m.
Le 27/06/2014 17:02, Neal Becker a écrit :
I don't think this is unique to mercurial.
I'd like to have 2 areas for installing extensions to a package: a system wide and a local.
I think the semantics we'd want is that the 2 trees are effectively merged, with the local overriding in the event of a conflict
Who is "we"? Mercurial extensions have to be enabled manually in your .hgrc, so whether they live in the hgext namespace or anywhere else is quite irrelevant. Regards Antoine.