per-branch configuration
Robey Pointer
robey at lag.net
Mon Feb 13 03:07:01 GMT 2006
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.)
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?
robey
More information about the bazaar
mailing list