[RFC] .bzrconfig directory

[Aaron Bentley]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Ian Clatworthy wrote:
> So I'm proposing we consider a new optional directory into which we
> begin putting/migrating special files. Here are some of the things I'd
> expect to see in there in the fullness of time:
> 
> 1. rules
> 2. ignores
> 3. (shell) hooks

Would that be a possible attack vector for malicious users?

> 4. branch.conf (not totally sure about this one)

Well, I've been feeling uneasy about branch.conf's specialness for a
while.  This wouldn't entirely fix it, because the other files you named
would be versioned files, and branch.conf must not be versioned.  But
it's worth considering.

Also worth mentioning is that my stacking policy work introduces another
source of configuration; a file named something like .bzr/config.conf

Right now, it only controls stacking policy, but it could potentially
also control whether working trees are created when branches are created
under this directory (the --no-trees flag to init-repo).

> Plugins may want to put things in here as well.

Right.  Shelf being one example.

> I think a separate directory is better because it can have its own
> namespace - one that makes sense to users - without being cluttered by
> the current .bzr files. E.g. a .bzrconfig directory might look like:

I don't think that's a great argument.  I'd argue for something like
this on the basis that users should not muck around in .bzr; .bzrconfig
would be somewhere they were supposed to muck around.

> Thoughts?

If we have a .bzrconfig directory, I would want it to exist whether or
not a working tree is present, even though it would be a versioned file
if the working tree was present.  Implementing that could get kinda ugly.

Aaron
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFINPIj0F+nu1YWqI0RAiwvAKCCUsajvC9QhgHtSEF/WBwBSvGKugCfX3eK
AcXtqeDPPnw9pMYItoFlDqg=
=2er+
-----END PGP SIGNATURE-----