[Bug 3940] New: Allow subrepos at a location that may not be within the parent repo folder

mercurial-bugs at selenic.com mercurial-bugs at selenic.com
Tue May 21 12:56:30 CDT 2013


http://bz.selenic.com/show_bug.cgi?id=3940

          Priority: normal
            Bug ID: 3940
                CC: mercurial-devel at selenic.com
          Assignee: bugzilla at selenic.com
           Summary: Allow subrepos at a location that may not be within
                    the parent repo folder
          Severity: feature
    Classification: Unclassified
                OS: All
          Reporter: bz.selenic.com at timwi.de
          Hardware: All
            Status: UNCONFIRMED
           Version: unspecified
         Component: Mercurial
           Product: Mercurial

Currently the Mercurial subrepo feature only allows the subrepos to be in a
sub-folder of the parent repo folder. For example:

   projectP/
   projectP/.hg
   projectP/.hgsub
   projectP/libraryA/
   projectP/libraryA/.hg

However, this precludes use-cases where several projects have the same
dependency, example:

   • Project P depends on Library A and Library B
   • Library A also depends on Library B

With Mercurial’s restriction, this scenario requires there to be two copies of
Library B, which is redundant.

I would prefer to have each project checked out once, and at the same level in
the file system:

   projectP/
   projectP/.hg
   projectP/.hgsub       # points to ../libraryA and ../libraryB
   libraryA/
   libraryA/.hg
   libraryA/.hgsub       # points to ../libraryB
   libraryB/
   libraryB/.hg

What would the ramifications be of lifting the restriction?

-- 
You are receiving this mail because:
You are on the CC list for the bug.


More information about the Mercurial-devel mailing list