Branko Čibej wrote:
> I think I'm finally seeing a light at the end if this tunnel. On
> Windows, the Registry is obviously the preferred location for
> configuration data. Typically, only developers will want to use a file
> (because editing the registry by hand is a royal pain). So I'd suggest
> we load the configuration in this order:
> * System-wide
> * User-specific
> Then we look at the options in the config "file" to see if there are
> more files to load. I'd even suggest a windows-specific section in the
> config file, like this:
> use-config-dir = C:/my-home-dir/.subversion
BTW, the nice thing about this is that, if I hack the Registry parser to
accept REG_EXPAND_SZ options, one can actually write
use-config-dir = %APPDATA%/Subversion
and automagically get the right directory. Yes, I know this brings env
var dependencies ...
> (or rather, that would be
> Then, if that option exists, try to load the file from that directory.
> I'll code this up if people agree.
> Alan Langford wrote:
>> At 2002/03/26 13:05 -0600, Karl Fogel wrote:
>>> If all Windows users think the Registry is sufficient, then I don't
>>> see much point going through contortions to figure out all possible
>>> for a file-based configuration area.
>> Goofy little files scattered all over the place are a pain in the
>> butt. Even with APPDATA present lots of users will want to put files
>> in different places. Meanwhile the registry has clean support for
>> system config data and user specific configurations, not to mention
>> easy ways to support multiple configurations.
>> Perhaps the best way to appease people with cross-platform issues is
>> to provide a facility to import/export config files from/to the
>> registry and let the users who need it do the job manually.
>> Alan Langford email@example.com
>> Ambit Perspectives (416)621-9899
Brane Čibej <brane_at_xbc.nu> http://www.xbc.nu/brane/
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Tue Mar 26 22:29:36 2002