Overlay repositories

[Wouter van Heyst]

On Fri, Sep 22, 2006 at 10:51:16AM -0400, Aaron Bentley wrote:

...

> Yes, and the behaviour of Steve's public location is what I considered
> similar to history horizons, the difference being that he doesn't even
> want the guarantee of having a subset.  He wants ghosts galore.
> 
> But history horizons already describes the notion of 'related
> repositories', from which ghost revisions may be retrieved.  That seems
> to be the core concept of overlay repositories.
> 
> > There are a few issues with chaining like this. For example: you are
> > probably accessing the branch over sftp, but other people are probably
> > more likely to access it over http. Well, for launchpad maybe not, but a
> > lot of times there would be a developers location and a public location.
> > So now the reference needs to have many different ways of referring and
> > indicating to the client which one they should be using.
> 
> Possibly.  But it's also a nice idea to allow multiple
> 'related-repositories' to be specified.  So maybe just specifying the
> sftp and http locations would be enough.
> 
> > I'd like to think about it a bit, and consider some internals and
> > implications. I think we could expand HistoryHorizons a bit for
> > something like this.
> 
> Yeah, I agree it could be done.  Personally I don't like the notion of
> changing bzr so that repositories are constantly dependent on other
> repositories that may or may not be accessible.  But this could even be
> implemented as a plugin.

This sounds very much like the Arch situation?

Wouter van Heyst