On Fri, 2009-11-20 at 13:28 +0100, Jiri Moskovcak wrote:
- load all plugins to determine which plugins do we have (as we can't
trust the config file :)) 2. enable (run init() at least I hope it works that way) only those plugins we want (listed in conf file)
So what is the proposal here? To load and enable all installed plugins?
Load and enable all plugins mentioned on 'EnabledPlugins = ...' line. Then, if while executing any other directive we see a plugin which is not loaded, load and enable it.
In C++ terms, "we see" means "GetAction(pluginName), GetReporter(pluginName), etc are called"
I was thinking about this and we still need to to have the option Enabled in per plugin configuration, to be able to disable them - e.g. disable the python plugin. We could leave it in the main abrt.conf, but it's getting quite complex and I think *Enabled = yes|no* is easier to parse/write then *EnabledPlugins = foo, bar, baz*
I think the location of "enabled" switch is not the topic of this thread, we are discussing whether it makes sense to remove the requirement that user must explicitly tweak "enable/disable" switch when he already specified that plugin Foo should be run.
I agree that "Enabled = yes/no" should be moved to per-plugin .conf file, I just did not get around to doing it yet.
-- vda