On 10/30/2015 12:46 PM, Dimitry Sibiryakov wrote:
> 30.10.2015 9:59, Alex Peshkoff wrote:
>> Not at all - if we decide to keep .conf files for plugins in
>> plugins/conf (or where-ever else) and use wildcard include in plugins.conf:
>>
>> include $(DIR_PLUGINS)/conf/*.conf
>>
>> Do you want me to do changes?
> Before doing that consider the case when two different plugins have
> setting with the
> same name but different meaning.
> It would be too cruel to make every plugin-related config file to use
> full syntax
> instead of simple "setting=value".
>
There are 2 types of plugin configuration - instructions for plugin
manager (read from plugins.conf) and internal plugin configuration
values. Placed into plugins.conf info is enclosed for each plugin into
{} braces:
Plugin=SomePlug
{
Name1=Value
Name2=OtherValue
...
}
When writing include file one anyway must have Plugin-Name and {} pair
in it, i.e. here we have no problems with mixed names. What about
internal configuration values - certainly your scenario is possible, how
we try to resolve conflicts in described in doc/README.plugins.html
------------------------------------------------------------------------------
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel
