[Opensim-dev] Ini file(s) loading

[krtaylor]

Actually, I thought it supported my point very well.  ;-)

I was not suggesting that the split ini in config be the only config 
option - I still like to override idea. But by default, users would edit 
the config/*ini, this does not stop a multi-region grid operator from 
syncing 20 override ini files to the bin of their regions.  My point was 
that there just should not be 2 places by default, one with default 
values and one with the overriding used values - that will just severely 
confuse the situation.

Kurt

Melanie wrote:
> And that brings us full circle to my proposal.
>
> There is much sense in a set of files that are used as defaults, and 
> then overriding settings in specific configuration files.
>
> Melanie
>
> Sean Hennessee wrote:
>   
>> I am one of those people that run trunk and update fairly often on 9 different 
>> OpenSim servers. I suspect I always will be. Having to manually merge two huge 
>> ini files, on 9 different servers, is a major pain. It would be even worse if I 
>> had to merge 6 or 8 different medium sized ini files on each of my 9 servers. 
>> Where they are located is not important to me, but I really would like to have 
>> an SVN new set of ini files, (or one ini file), with all the latest changes that 
>> is read first, and a way for me to have a small ini file that I can use for my 
>> specific settings which will override the default ini settings. That would make 
>> my life much much easier.
>>
>> Peace,
>> Sean
>>
>> Jeff Ames wrote:
>>     
>>>> Just splitting up the file and putting it in config, with all the
>>>> comments, would help. And for the SVN update - that is a problem
>>>> with any modifications to the tree, not just config. That's what
>>>> backups are for. I guess a simple backup/diff tool for config would
>>>> be a quick solution...
>>>>     
>>>>         
>>> Just have config/*.ini and let conflicts happen as they come?  I kinda
>>> agree... If you're updating some application from version 1.0 to 2.0,
>>> you expect to have to merge your config changes.  I imagine part of
>>> the merge problem is just that people are running trunk and updating
>>> all the time rather than using the (too infrequent?) tagged releases.
>>>
>>> I'm +1 on just using config/*.ini directly.
>>>
>>> Jeff
>>> _______________________________________________
>>> Opensim-dev mailing list
>>> Opensim-dev at lists.berlios.de
>>> https://lists.berlios.de/mailman/listinfo/opensim-dev
>>>
>>>   
>>>       
>> -- 
>>
>> Sean Hennessee
>> mailto:sean at uci.edu
>> http://www.nacs.uci.edu/~sean
>> Central Computing Support
>> Network & Academic Computing Services
>> UC Irvine
>> (949)824-8225 Office
>> (949)293-5224 Cell
>>
>>
>> ... . .- -. /  .... . -. -. . ... ... . .
>>
>>
>>
>> ------------------------------------------------------------------------
>>
>> _______________________________________________
>> Opensim-dev mailing list
>> Opensim-dev at lists.berlios.de
>> https://lists.berlios.de/mailman/listinfo/opensim-dev
>>     
> _______________________________________________
> Opensim-dev mailing list
> Opensim-dev at lists.berlios.de
> https://lists.berlios.de/mailman/listinfo/opensim-dev
>   

-- 
Kurt Taylor (Kurt Stringer)