On Fri, 04 Feb 2000 13:30:04 EST, the world broke into rejoicing as
"James A. Treacy" <[EMAIL PROTECTED]> said:
> Doesn't the following satisfy all the points brought up so far?
> Program looks for the following in order. Later entries will override
> earlier ones:
>
> /etc/gnucash.conf (may be symlinked into /usr/share/etc/)
> ~/.gnucash/* (may be a dir. Not important for the point I'm making)
> ./.gnucash/*
>
> I believe that many programs use a system similar to this.
>
> There are two ways we can handle deciding between saving to ~/.gnucash
> and ./.gnucash:
>
> Settings are saved to ~/.gnucash unless the user has created ./.gnucash,
> in which case they are saved there. This allows the power user to create
> different defaults, while keeping the default simple.
> or
> When saving settings a dialog could come up asking whether the settings
> are global. If not, they are saved to the current dir.
>
> The only problem here is what to do if a sysadmin wants to set up
> some system defaults that can't be overidden. Does that even make
> sense for a program like gnucash?
The real question here is whether we have:
a) Layered sets of configuration, or
b) At the end of it all, *one* configuration file that controls
things.
I *think* that with GnuCash, we effectively have the latter.
That approach implies that the ordering probably ought to be to go
from the most specific possible configuration (./.gnucash) to the
least specific (/etc/gnucash.conf).
That is the reverse of what happens with (for instance) zsh, where the
system starts by reading config from /etc/zshenv, /etc/zshrc, and then
moves on, loading *all* config files in the hierarchy, gradually
moving from most generic to most specific.
I don't think it'll be too difficult to ask/answer the questions
relevant to making sure we know which ordering is most appropriate.
In either case, we can have a reasonably logical way of either:
a) Sequencing which set of configuration to load in next, such as
/etc/gnucash.conf, /usr/local/etc/gnucash.conf,
$HOME/.gnucash/gnucash.conf, ./.gnucash/gnucash.conf
or
b) Setting up a list like the above, and traversing it in reverse
order, stopping as soon as a config file is found.
--
Women who seek to be equal to men lack ambition.
[EMAIL PROTECTED] - - <http://www.hex.net/~cbbrowne/lsf.html>
--
Gnucash Developer's List
To unsubscribe send empty email to: [EMAIL PROTECTED]
