[PATCH] cascading lookup support in LocationConfig (bug 33430)

[Robert Collins]

On Wed, 2006-09-20 at 08:53 +0800, James Henstridge wrote:

FWIW the current behaviour really is a bad compromise. I think Martin
and I had sufficiently different mental models of the config that when
we compromised it came out -badly-.

We may not be able to do a -really nice- file format now without
breaking compatability. So I have a suggestion:

Sketch out use cases for what you are trying to preserve, and what you
are trying to have happen. We can all weigh in on those - which is an
extension of the design discussion thats already happening - and finally
we can decide if syntax compatability with current configs is worth
paying whatever price we expect to have to pay for the common case.

For my part I think the following are the key things:

bzr branch within a repository should be able to write a new section,
but still inherit from the repositorys location settings.

bzr push to a remote branch should be able to get a default rpush
location from location.conf and then push to the same relative path
within that target, likewise with pull.

Remember in building this that repositories should be *just* a storage
optimisation : there should be no need for a repository to get the
convenience of cascaded settings.

for example if I have location.conf:
[/home/robertc/source/bzr/]
push_location = sftp://people/~/public_html/baz2.0

then
$ cd /home/robertc/source/bzr
$ bzr init new-branch
$ cd new-branch
$ bzr push 
Using remembered location: sftp://people/~/public_html/baz2.0/new-branch



-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: 191 bytes
Desc: This is a digitally signed message part
Url : https://lists.ubuntu.com/archives/bazaar/attachments/20060927/2f886922/attachment.pgp