There seems to be a bit of a theme of plugins classifying themselves as non-interactive (TYPE_CORE) but still depending on some of the pieces presented by the cli, especially with regards to option parsing. This leads to pretty regular tracebacks for pirut and other non-cli users :(
The question is what can we do to make plugins more reliable for other API users. Do we a) just punt on the use of plugins from non-cli users[1] and disable plugins there b) suck it up and add at least a dummy command line for other API users so that plugins can expect to always be able to access it[2] c) add some form of checking and raise errors if plugins do things with the command line but are of type TYPE_CORE. This would at least make it so that they would also traceback for cli users and thus hopefully avoid some of the problems d) something else? Jeremy [1] Well, this would likely end up being "add a list of allowed plugins" and let the tool define which plugins it would allow [2] This is what I went ahead and did yesterday in pirut after duping a dozen bugs -- http://git.fedorahosted.org/git/?p=pirut.git;a=commitdiff;h=8fc42a6e0accffc694ba5d33dcf17d772e920d27 _______________________________________________ Yum-devel mailing list [email protected] https://lists.dulug.duke.edu/mailman/listinfo/yum-devel
