per-branch configuration

[Jan Hudec]

On Sun, Feb 12, 2006 at 19:07:01 -0800, Robey Pointer wrote:
> Currently there are two incompatible ideas about how to store  
> configuration (preferences) specific to a single branch.
> 
> 1. Store in ~/.bazaar/branches.conf, away from the branch folder,  
> using the folder name (like "/home/robey/code/bzr.dev") as the key  
> identifying the branch.
> 
> Con: The branch configuration is invisibly tied to the folder on your  
> disk, and if you move the branch folder, your config doesn't follow  
> you.  This violates the principle of least surprise.
> 
> 2. Store in .bzr/ inside the branch.
> 
> Con: Doing a "cp -a" or "zip -r" of the branch will also copy the  
> configuration, which may be wrong if you want to use a different  
> identity per branch.
> 
> (I'm not sure I captured the "con" of #2 correctly so please correct  
> if there are other reasons.)
> 

 3. Store in ~/.bazaar/branches.conf, but key on branch nick.

> Today it occurred to me that maybe the issue could be sidestepped by  
> using branches.conf, but keying by branch nickname instead of folder  
> name.  Then the config isn't tied to the folder layout, and doing a  
> "cp -a" only requires you to set a new branch nick to avoid using the  
> same config.
> 
> What do you all think?

I personally vote for 2. When I copy a branch, it will usually get a new
configuration anyway. Whether I overwrite old setting or not is not much
important.

Besides, currently we are doing half of 1 and half of 2. The push target
is in ~/.bazaar/branches.conf, but the pull-source is in the branch
itself and so is the branch nick.

-- 
						 Jan 'Bulb' Hudec <bulb at ucw.cz>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : https://lists.ubuntu.com/archives/bazaar/attachments/20060213/6c8f0fb7/attachment.pgp