[Yum-devel] single line config files for plugins

James Bowes jbowes at redhat.com
Mon May 7 19:41:50 UTC 2007


Jeremy Katz wrote:
> It should be pretty straight-forward to get plugins to load
> automatically...
> 
> Basically, we'd need to change plugins.py:_loadplugin() so that it
> defaults to continuing rather than saying the plugin is disabled.  We
> could then also add a check for a 'default_enabled' attr in the module
> if we wanted.  Something like the following completely and utterly
> untested patch.

I don't think that attr is necessary. Is anyone really going to want
their plugin to be disabled by default? Maybe, but only if there was a
--enableplugins=GLOB command-line option (I call no-writesies!).


> 
> Could even go one step further and make a new plugin API version add the
> "on by default"-ness and then check the plugin version.  Which probably
> makes some sense.  In any case, it doesn't feel like 3.2.0 material to
> me.

Meh. Every existing plugin has their own config file, so doing this
won't change anything, really.

Where is 3.2.0, anyways?

-James

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 251 bytes
Desc: OpenPGP digital signature
Url : http://lists.baseurl.org/pipermail/yum-devel/attachments/20070507/94dac6c6/attachment.pgp 


More information about the Yum-devel mailing list