should have a system-wide configuration file (/etc/bazaar/bazaar.conf etc)

We also talked about having a project-wide configuration file, there may be room for both, but it can become
hard for a user to understand what is happening when the an option is specified in more than one file.

So we may also need to add the necessary UI to display where a config variable is defined and which of the definitions
is taken into account when. That may be a simple -Dconfig flag so that it's available for every command.

Another possibility will be to allow some form of '#include' in configurations files.

Hi Thomi,

On Tue, 2011-07-26 at 08:33 +0000, Thomi Richards wrote:
> ** Changed in: bzr
> Assignee: (unassigned) => Thomi Richards (thomir)

Vincent is also doing a lot of work on the configuration infrastructure
at the moment, including looking at a global configuration file. It
might be good to coordinate with him, although he is on vacation this
week.

Cheers,

Jelmer

I think Vincent posted and merged all his work. I wouldn't block on him.
On Jul 26, 2011 7:31 PM, "Jelmer Vernooij" <email address hidden>
wrote:
> Hi Thomi,
>
> On Tue, 2011-07-26 at 08:33 +0000, Thomi Richards wrote:
>> ** Changed in: bzr
>> Assignee: (unassigned) => Thomi Richards (thomir)
>
> Vincent is also doing a lot of work on the configuration infrastructure
> at the moment, including looking at a global configuration file. It
> might be good to coordinate with him, although he is on vacation this
> week.
>
> Cheers,
>
> Jelmer
>
> --
> You received this bug notification because you are a member of bzr-core,
> which is subscribed to Bazaar.
> https://bugs.launchpad.net/bugs/419854
>
> Title:
> should have a system-wide configuration file (/etc/bazaar/bazaar.conf
> etc)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/bzr/+bug/419854/+subscriptions
>