Bug 1088235

Summary:	[vote] [rfe] option to disable selected plugins
Product:	[Fedora] Fedora	Reporter:	Tim Lauridsen <tim.lauridsen>
Component:	dnf	Assignee:	Packaging Maintenance Team <packaging-team-maint>
Status:	CLOSED NOTABUG	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	20	CC:	akozumpl, packaging-team-maint, pnemade, rholy, tim.lauridsen
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-05-02 05:42:29 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Tim Lauridsen 2014-04-16 09:43:58 UTC

Description of problem:

By default every plugins installed on the system is enabled.
It would be very useful if there was a way to disable some plugins
temporary or permanently.

a --disableplugins cmdline option is a posibillty, but a better way
is properly to add an disabled_plugins option to dnf.conf

it can be set by using --setopt disabled_plugins=plugin,plugin is a temporary disable is needed


Version-Release number of selected component (if applicable):
0.4.20

Comment 1 Ales Kozumplik 2014-04-16 14:00:01 UTC

Tim, I take it it is something you'd appreciate as a plugin developer. I am however not convinced adding options like this provides enough value for specific use-cases to a regular user that would be worth the added complexity in CLI code and especially in the user documentation.

Proposing this up to CC vote with an outlook of closing this as WONTFIX.

Comment 2 Tim Lauridsen 2014-04-16 17:12:35 UTC

when plugins are bundled like in dnf-plugins-core, there is a potentiel risk that a plugin can interferre with another plugin from another package and the only workaround is to remove one of the packages contain the plugins or do dirty stuff
like renaming/deleting the plugin from the filesystem.

Personal, I can handle it, but it would be nice for other users to be able do workaround such issues, without having to remove all plugins in a package, because one is givning problems.

Comment 3 Ales Kozumplik 2014-04-17 06:45:24 UTC

(In reply to Tim Lauridsen from comment #2)
> when plugins are bundled like in dnf-plugins-core, there is a potentiel risk
> that a plugin can interferre with another plugin from another package and
> the only workaround is to remove one of the packages contain the plugins or
> do dirty stuff
> like renaming/deleting the plugin from the filesystem.

Plugins interfering is a pathological scenario, i.e. bug. It is up to us to deliver plugins bugs-free, not up to the users to pick&choose which plugins currently work to run with.

Comment 4 Tim Lauridsen 2014-05-01 10:24:45 UTC

Missed the fact that dnf already has a --disableplugin [plugin] commandline option
so fell free to close this one

Comment 5 Ales Kozumplik 2014-05-02 05:42:29 UTC

Thanks.