[rfc] more control over activating fallback repositories (aka what gets stacked on)

[Robert Collins]

On Wed, 2008-10-08 at 18:21 +1300, Michael Hudson wrote:
> Currently, opening a branch also opens any stacked on branch specified
> in the branch's branch.conf file.  This is inconvenient some of the
> time, particularly in the innards of the codehosting system on Launchpad
> where we want to be able to inspect and maybe interfere with the stacked
> on URL before opening what it points at.

There are a bunch of other places you could do this - you could patch
into the transport logic. What sort of transforms do you want to do?

> A reasonable way to do this seems to be to add a
> "dont_activate_fallbacks" (or similarly named) to Branch.open and
> related functions (and then our code would be responsible for calling
> add_fallback_repository with appropriate arguments.

I don't think this is good, because its a dangerous facility that will
lead to incorrect behaviour if misused; if the fallback is not available
the branch and repository are not complete and are unable to be used.
I'd support some mechanism to let you /alter/ what url is used, but not
one to disable/enable it.

-Rob
-- 
GPG key available at: <http://www.robertcollins.net/keys.txt>.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url : https://lists.ubuntu.com/archives/bazaar/attachments/20081009/bf245d47/attachment.pgp