[Opensim-dev] Autocreated OpenSim.ini

[Stefan Andersson]

Uh. Another approach would be to actually use the 'merge' functionality of nini so that we could have the .example as a fallback defaults file.

(It should then probably not be called '.example' but rather '.default')

So, by just adding another line of code, we'd have opensim.ini as an optional local override of entries in opensim.default - then we can change and add to opensim.default, and peoples local changes are kept untouched. The startup can create an empty opensim.ini (with just a comment with an url to a wiki page or something) if there is none on start.

(All this provided the opensim.ini is actually parsed by nini, but if it isn't, it should be)

Best,
/Stefan




Date: Thu, 13 Mar 2008 21:57:24 +0100
From: DrScofield at xyzzyxyzzy.net
To: opensim-dev at lists.berlios.de
Subject: Re: [Opensim-dev] Autocreated OpenSim.ini








Alan M Webb wrote:


  I think that's a great idea. I was
pondering
it myself; I think the code generated file approach is absolutely the
wrong
way to do it.
  

  

  Given the merging capabilities of
the
config mechanisms couldn't we set it up to merge startup.ini (if it
exists)
after the example .ini? That way we would get overrides if they exist,
and defaults if they don't without doing any conditional copying or
munging
of files. The startup.ini can then be written out by the config
mechanism
if it didn't already exist, or if the configuration has been changed.
  


that sounds like a rather good idea!



    cheers,   

    dirk



-- 
dr dirk husemann, mathmatics and computer science, ibm zurich research lab
SL: dr scofield ---- drscofield at xyzzyxyzzy.net ---- http://xyzzyxyzzy.net/
RL: hud at zurich.ibm.com - +41 44 724 8573 - http://www.zurich.ibm.com/~hud/



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://opensimulator.org/pipermail/opensim-dev/attachments/20080313/1d7b1c91/attachment-0001.html>