stack-based configuration files road-map

[vila]

>>>>> Martin Pool <mbp at canonical.com> writes:

<snip/>

    >> Since they depend on BZR_HOME, that shouldn't be an issue.

    > It will be for the system-global file that Grid is adding.

Ha, right, yeah, forgot that one (even if I mentioned it in the review
;)

<snip/>

    > I was thinking that it's just inefficient to do disk IO when we know
    > there's nothing interesting there; but obviously this is not urgent.

And probably a premature optimization compared to the fact that we read
a config file for every option *today*, reaching the point where a
config file is read only once (even if it doesn't exist) will already be
the most significant progress.

    >> 
    >>    >  * it would be useful to have a clean way for tests to see what
    >>    > happens when a particular value is configured
    >> 
    >> Yup. I'm still unclear on how we will use that but that's definitely
    >> something I want to investigate.
    >> 
    >>    >  * some tests for configuration itself will be exceptions
    >> 
    >> What do you mean by configuration here ?

    > Tests that the configuration stack really does go to disk, to the
    > user's directory, etc.

Right, basic unit tests then, I think we have adequate coverage so far
but feel free to contradict me ;)

    Vincent