.bzr.conf

[John A Meinel]

Martin Pool wrote:
> The user experience for creating ~/.bzr.conf/email is a bit ugly and
> hard to get right.
>
> We use the directory because it was previously suggested that people
> dislike programs that create a lot of files in their home directory --
> it's considered better to just make one directory and put everything in
> there.  That's a fair point but it does make it a little harder.
>
> The directory is not called .bzr because we don't want to confuse it
> with a control directory: people might want $HOME to be version
> controlled and even to put their bzr configuration in version control.
>
> Subversion uses ~/.subversion/ (by contrast to .svn for version
> control).  This directory seems to be automatically created containing a
> readme and some skeleton files.  Maybe that's a good idea.
>
> Perhaps we should follow that pattern and call it ~/.bazaar?
>
> We could also prompt for an email address when first run if it's not
> set.
>

I'm alright with ~/.bazaar, though ~/.bzrrc and the current ~/.bzr.conf
are also fine with me.

As far as conflicting with baz-1.x it seems like baz-1.x is using
~/.arch-params already, and as time goes on it is planning on merging
with baz-ng, so they can both use ~/.bazaar without conflicting.

As far as automatically setting "$BZR/email" what about respecting
$BZREMAIL and $EMAIL?

And finally, I agree it might be nice to have per project configuration,
so that per tree you can have a unique address.

I would not set that one automatically, because you might change your
default email address, and have to go around changing it everywhere.

John
=:->
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 253 bytes
Desc: OpenPGP digital signature
Url : https://lists.ubuntu.com/archives/bazaar/attachments/20050728/705ca08a/attachment.pgp