Re: [Roundup-devel] config.ini

[Richard J. <ri...@co...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 26/07/2004, at 5:50 PM, alexander smishlajev wrote:
> Richard Jones wrote, at 26.07.2004 10:29:
>> A problem I've just thought of is that some tracker templates might 
>> want to have additional config vars in their config.ini - to control 
>> some behaviour in their detectors or whatever. Something to think 
>> about ;)
>
> definitions for any additional options must be added to the Config
> object in OldStyleTrackers.open() before config.load() is called.  
> (this
> means that config should be created without passing the tracker_home 
> value.)
>
> currently Config objects have .add_option() method accepting instances
> of the Option class (or it's heirs).  perhaps we could publish a method
> like add_section(), accepting a section name and definition list in the
> same format as used in configuration.SETTINGS now.

Perhaps we just have to require that tracker templates *can't* add new 
config options to the config.ini? If they have any configuration, then 
it's done in the detector (or other) modules. The config.ini could be 
only for Roundup internal configuration...


      Richard
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (Darwin)

iD8DBQFBBamYrGisBEHG6TARArxqAJ9VkcMvhQ7M+nv5cvDktNSeX7si4wCff9aZ
NUBHECCwbkqUUk5nuS0+nXQ=
=jDub
-----END PGP SIGNATURE-----