thoughts on a bzrrc file

[Dafydd Harries]

Ar 19/05/2005 am 08:49, ysgrifennodd Magnus Therning:
> On Thu, May 19, 2005 at 05:27:51PM +1000, Benno wrote:
> >On Thu May 19, 2005 at 17:12:46 +1000, Martin Pool wrote:
> [..]
> >>----------------
> >># my bzr config file
> >>
> >>diff_program = diff -uw %s %s
> >>email = Martin Pool <mbp at sourcefrog.net>
> >>editor = emacsclient %s
> >>
> >
> >How about the option of having a ~/.bzrrc.py file for those that want
> >to script settings. I think my previous example had setting a different
> >email based on the project. E.g:
> >
> >if (project_is_about_work):
> >  email = me at work
> >else: 
> >  email = me at home
> 
> Is there some other (non-programming) way of adding per-project
> settings?
> 
> First I was thinking of personal defaults in ~/.bzrrc and per-project in
> the working area but for obvious reasons that wouldn't be very good.
> 
> Maybe it'd be possible to put several config files in ~/.bzr/?
> For projectA we'd first load ~/.bzr/bzr.conf and then let things in
> ~/.bzr/projectA.conf override... I guess I should put some code behind
> all this rambling instead.

I think it's wise to put configuration in its own directory. Even if you
only need a single file at first, this often changes with time. ~/.bzr/
would be a good place for storing keyrings when bzr starts supporing GPG
authentication, for instance.

-- 
Dafydd