[Opensim-dev] OpenSimDefaults.ini clean up

[James Stallings II]

Actually Mel, I would not suggest that you do so. I've found some fairly
useful workflows involving the shell utilities find, diff, grep and sed
that really kind of move such concerns aside, allowing me to analyze and/or
edit large groups of files all in one big glorious command line invocation
:3

Note that heavy CYA safety nets are in place ;)

It isn't especially advanced by way of technique what I'm doing, really
just using those tools together for their intended purposes.

If someone does get around to writing a gui configurator, that would be
awesome (/me pokes marcus)

Sorry for the confusion about the proprietary nature of the thing Mel, I
guess I got the wrong idea last time we spoke of it, and that has been
quite some time.

In any case, my strategy is basically to use grep as a filter to get rid of
the 'comments' on the fly, single out things I need to compare, etc which I
then pass to diff or sed. I use find to generate lists of paths to the
files I need to compare or edit (or not, depending whether I'm working on
files in bulk).

It's kind of a cowboy way of doing things, but it's very quick and
effective if you don't get too crazy with it. Safe too if you make sure to
keep good backups.


Cheers!
James/Hiro



On Tue, Apr 8, 2014 at 11:43 AM, Marcus Llewellyn <
marcus.llewellyn at gmail.com> wrote:

> In regard to the specially formatted comments meant to aid external
> configuration tools, it may be worth considering adding these to
> OpenSimDefaults.ini. Currently, OpenSim.ini.example contains them, but
> OpenSimDefaults does not.
>
> When one strips OpenSim.ini.example down to *only* active sections, keys,
> and values while including those configuration comments, you end up easily
> seeing that every single option is being paired with a special
> configuration comment.
>
> On the other hand, if you do the same thing to a grid's OpenSim.ini file
> (I used OSgrid's), it becomes much less consistent. Sections like Startup
> or XEngine will only have a few of these config/option pairings. Some
> sections like RegionReady, VivoxVoice, and BulletSim have none at all. The
> authors of these OpenSIm.ini files aren't at fault. They simply have more
> imperative things to do than track down all of the possible option values
> or dependencies.
>
> Since, presumably, options added to OpenSim.ini files like OSgrid's are
> largely derived from OpenSimDefaults.ini, it could be of benefit to provide
> the config comments in OpenSimDefaults as well. OpenSim.ini.example is
> setup only for standalones. Simulators configured for grids obviously use
> more options (about 7 times the options in OSgrid's case). Any future
> configuration tool would probably be most useful on configuration files
> meant for either mode of operation.
>
> _______________________________________________
> Opensim-dev mailing list
> Opensim-dev at lists.berlios.de
> https://lists.berlios.de/mailman/listinfo/opensim-dev
>



-- 
===================================
http://osgrid.org/
http://simhost.com
http://twitter.com/jstallings2
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://opensimulator.org/pipermail/opensim-dev/attachments/20140408/8fe1279d/attachment-0001.html>