Subrepos and multiple top repos

Martin Geisler mg at lazybytes.net
Wed Jun 1 05:08:47 CDT 2011


Thomas De Schampheleire <patrickdepinguin+mercurial at gmail.com> writes:

> On Wed, Jun 1, 2011 at 8:35 AM, Martin Geisler <mg at lazybytes.net> wrote:
>> Mathias De Maré <mathias.demare at gmail.com> writes:
>>
>>> I currently see the following options:
>>> - store all the repositories in the same top-level directory, and put
>>> symlinks in the top repositories to the subrepositories
>>> - patch the server to always return a top-level directory, even when clients
>>> request a subrepository down a few levels
>>>
>>> Both of these seem quite annoying.
>>> - The first requires adding new symlinks whenever a new subrepository is
>>> added (or moved from one directory to another!).
>>
>> You'll need to log into the server anyway in this case: you cannot
>> create new (sub)repositories on a server without a login.
>
> This is not always true: if you use a tool like mercurial-server [1],
> you can create remote repositories over ssh. Everyone uses the same
> ssh account, but authentication happens based on personal key-pairs.

Sure, you can write a tool that will do the "log into the server" part
for you, so to speak.

Maybe mercurial-server could support creating subrepos somehow: you tell
it you need a subrepo at /proj/X and that the real repo is at /X. It
then makes the symlinks or share the repo as necessary on the server.

> Thomas
>
> [1] http://www.lshift.net/mercurial-server.html

-- 
Martin Geisler

Mercurial links: http://mercurial.ch/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: not available
URL: <http://selenic.com/pipermail/mercurial/attachments/20110601/b2584294/attachment.pgp>


More information about the Mercurial mailing list