Global shared repositories

[Ville M. Vainio]

On Wed, Mar 12, 2008 at 3:18 PM, John Arbash Meinel
<john at arbash-meinel.com> wrote:

>  You would suffer a bit putting your 100 revision plugin next to your 10k
>  revision program. Just because some operations on the plugin are going to have
>  to search through the revisions for the program and discard them. Most of that
>  should only be in O(log(N)) space, not O(N). (In O(N) it would be 10,100 versus
>  100, while in O(log(N)) it is 4 versus 2, so 2x slower, not 100x).

I suppose you can't get around this by grouping the packs by some
magic cookie, e.g the hash from the first revision, creating a
subgroup to search first and from which the pack would most likely be
discovered?

>  Probably the biggest reason not to do it is discoverability from a remote
>  connection.

But this is not an issue with bzr+ssh, right?

>  Also, someone else pointed out using a --no-trees repository with lightweight
>  checkouts, which allows you to keep your revision storage separate from your
>  working location. We certainly would like to make working in this mode easier.

I'll look into that, but so far Alexander's suggestion of just putting
the repo to c:\ will work for me. Perhaps that is something you could
add to tutorial as well - it is not obvious from the beginners docs
that shared repositories don't in any way require you to create an
additional directory layer, or worse, have multiple shared
repositories, one for each project.

-- 
Ville M. Vainio - vivainio.googlepages.com
blog=360.yahoo.com/villevainio - g[mail | talk]='vivainio'