Nested repos

[Matt Mackall]

On Fri, 2009-07-17 at 01:31 -0700, John Patterson wrote:
> Hi,
> 
> I am using hg hg 1.2.1 which is the current macports package. I have a
> number of code modules shared between several larger projects.  Each has its
> own repo and so do the larger projects that use these modules.  I want each
> larger project to have its own version of the modules so that as releases
> are made they always include the correct state of the modules.  I also don't
> want to break other projects using the modules or be forced to modify them
> when the shared versions change.
> 
> /ModuleA
> /ModuleB
> /LargeProject1
> /LargeProject1/ModuleA
> /LargeProject1/ModuleB
> /LargeProject2
> /LargeProject2/ModuleA
> /LargeProject2/ModuleB
> 
> I expected this to work without the new subrepos feature because when I
> commit a large project I do not want any special handling of the included
> modules.  They should also be included in the large projects repository. 
> However what I have found is that code in /LargeProject1/ModuleB is not
> included when I issue a hg status.
> 
> Is there some way around this?

No, Mercurial will steadfastly refuse to look at files in a nested
repository. Short of fiddling with union mounts or similar, there's no
way around it. As far as I know, you're the first person to ask for this
particular behavior variant.

-- 
http://selenic.com : development and support for Mercurial and Linux