On Sat, Apr 25, 2015 at 08:57:19AM +0200, Martin Sourada wrote: > V Mon, 13 Apr 2015 21:20:49 +0100 > "Richard W.M. Jones" <rjones@xxxxxxxxxx> napsáno: > > > On Mon, Apr 13, 2015 at 02:17:14PM -0500, Bruno Wolff III wrote: > > > On Mon, Apr 13, 2015 at 17:49:45 +0100, > > > "Richard W.M. Jones" <rjones@xxxxxxxxxx> wrote: > > > > > > > >Anyway, here is the BZ: > > > >https://bugzilla.redhat.com/show_bug.cgi?id=1211344 > > > > > > I filed https://bugzilla.redhat.com/show_bug.cgi?id=1208626 > > > previously. You can disable it on the command line for scripting. > > > > OK, but I think it's better if all dnf plugins understand 'dnf -y', > > otherwise we'll end up having to have a pile of --disableplugin hacks > > for every badly behaved plugin. > > > > Rich. > > > > And what should be the behaviour in this one? Clearly -y assuming Y for > the plugin in question is very dangerous because it would replace all > your configs that were updated in the upgraded package(s). > > I agree it would make sense for this plugin to be turned off by > default, it's dangerous if used without caution, although I also agree > it can be a very useful plugin, cause you can spot config changes in > nicely formatted way (diff) during upgrade(s) and see if there's any > problem if left without attention (our policies for updates and update > QA are one of the best out there, but there can still be some slippage > or during distro upgrade this can happen as well...). As you say, I don't think that just installing dnf-plugins-extra should enable this plugin. Some extra step should be required. That also makes 'dnf -y' safe. Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com virt-df lists disk usage of guests without needing to install any software inside the virtual machine. Supports Linux and Windows. http://people.redhat.com/~rjones/virt-df/ -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
