[Yum-devel] single line config files for plugins

[seth vidal]

On Tue, 2007-05-08 at 09:28 +0200, Tim Lauridsen wrote:
> James Bowes wrote:
> > Most plugins come with a config file that only includes 'enabled = 1',
> > why bother making them ship this config file?
> >
> > Maybe instead we should just enable any plugin that doesn't have a
> > config file, preferably doing it in a way that breaks API?
> >
> > -James
> >
> >   
> I not sure this is a good ways to go, if a plugin don't have a conf 
> file, what do a user do if he want to disable a plugin temporary.
> I don't think it is a big problem to add a conf file while packaging 
> plugins.
> If plugins are enabled by default there should be a easy way to disable 
> them.
> 
> Here is some ways it can be done.
> * add a disableplugins=plugin1,plugin2 to yum.conf
> * add 'yum disableplugin <pluginname>' command, it sets 'enable=0' in 
> the plugin conffile, it it dont exists then it is created.
> 
> If there is a easy way to  disable the plugins, without the user have  
> to create a conf file by hand and set 'enabled=0', then it will be fine with
> me to make the plugins enabled by default if the conf file dont exist.
> 

playing catch up with old email.

 I just wanted to say I agree with Tim's point. It adds another barrier
for the user. Let's work on the option to disable specific plugins from
the cli and leave the plugins with a simple conf file.

-sv