[Yum-devel] plugins and pain
Michael E Brown
Michael_E_Brown at dell.com
Wed Jan 16 17:47:05 UTC 2008
On Mon, Jan 14, 2008 at 04:19:36PM +0100, Tim Lauridsen wrote:
> seth vidal wrote:
> >On Mon, 2008-01-14 at 09:32 -0500, Jeremy Katz wrote:
> >>On Mon, 2008-01-14 at 09:18 -0500, seth vidal wrote:
> >>>Talking to Tim about plugins on the irc channel it occurred to me, to
> >>>keep interactive plugins from damaging not interactive program
> >>>executions we should keep from loading them, at all, ever.
> >>>However, we have to load them a bit to inspect what type of plugin they
> >>>are. What if we put the plugin type in the plugin config file. Scan the
> >>>config files for the type and ignore the ones which won't work for
> >>>whatever interface we're using at the time. If we don't find the plugin
> >>>type defined there then we can fallback to loading the plugin - for
> >>>compat reasons.
Are plugins doing things on import that break stuff? If so, tell plugin
authors to not do that.
If it is really necessary to do this, can we do it in a way that doesnt
make forward/back compat a big pain?
More information about the Yum-devel