.local config files

[Joost van Baal]

On Wed, Sep 19, 2001 at 10:56:21AM -0400, Francis J. Lacoste wrote:
<snip>
> 
> The only configuration there is now that is specific to the superservice
> is the report configuration file (<superservice>.cfg). This file
<snip>
> The way to change it without modifying the system file is to modify
> a copy of <supservice>.cfg and put that copy in $HOME/.lire/etc/
> 
> This means several things :
> 
> 1) Modifications aren't lost after an update 
>    (it doesn't touch $HOME/.lire/etc)
> 
> 2) There are no way to make site-wide local customization. That could be
>    fixed by looking for a <sysconfdir>/lire/etc/<supservice>.cfg.local
>    file before taking the defaults, if you think it is a needed functionality.

Nah, I don't think we really need it.  Generally, there'll be only one
lire user anyway.

> 3) There are no way to customize only one parameter while taking automatically
>    the rest of the configuration. For example, after an update, the new
>    reports won't be automatically added to the customized report.
> 
>    Personnally, I think that having all the report's customization in one
>    file is easier to grasp for the user then an indirected customization 
>    in several files. It gives less granularity but I think the
>    tradeoff is good. Running lr_config after an update could be a way to
>    see that there are new repots available and add it to the customized
>    report.

Hmm...  I'm not really sure about this.  Of course, the time we'd have
to spent on coding the functionality is also to be taken into account :)
(Ideally, lr_config would _read_ local configurations before starting
to write a new local config file.)

One could argue that we should get rid of .../etc/lire/defaults.local
_also_, to offer a consistent configutation framework.  I'm not sure
about this neither, however...

> 4) I don't know if there is a need to modify global parameters on a 
>    superservice level. (Like to modify INCLUDE_IMAGES only in a specific
>    supservice) If this is the case, we could add sourcing of
>    <sysconfdir>/lire/defaults.<superservice>  or 
>    <sysconfdir>/lire/<superservice>/defaults.local for backward compatibility.

I agree, we don't need this.  It's too baroque.

BTW, do you feel like upgrading lr_config to the current configuration
files?  I believe that should be done before we can ship.

Bye,

Joost


-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 232 bytes
Desc: not available
Url : http://lists.logreport.org/pipermail/development/attachments/20010923/12beb3ee/attachment.bin