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. > > > > Thoughts? > > If it's in the config file, users are going to think they can change it > and have the change be useful/meaningful... :-/ >
it will be meaningful. It will mean that their system will break. :) okay, then failing that we setup a plugins-type directory in /usr/share that has this info. -sv _______________________________________________ Yum-devel mailing list [email protected] https://lists.dulug.duke.edu/mailman/listinfo/yum-devel
