Description of problem:
Currently the mock plugin api isn't really a plugin api. That is, the explicit
list of plugins is spelled out in the mock sources, meaning it's not easily
extendible with new plugins. It would be better if mock trolled its plugin
directory and loaded all plugins that were available.
The current workaround I'm using (sort of a hack) is to manipulate the plugin
list and plugin configuration dictionaries from the site-defaults.cfg file.
That's a short-term solution, since the newly-added plugins aren't visible from
the command-line enable/disable options.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Agreed. I originally started working on the plugin API, but my intent was to
ensure that I didnt over-engineer it and write a bunch of code that would not be
If you have specific enhancements to the plugin API, go ahead and post them to
fedora-buildsys-list for discussion, and I would more than happy to add any
reasonable extensions to the plugin API to the codebase.
*** This bug has been marked as a duplicate of bug 634224 ***