On 07/14/2017 10:32 PM, Matthew Miller wrote:
On Fri, Jul 14, 2017 at 07:25:11PM +0100, Richard Hughes wrote:
> Maybe tangential to the proposal/discussion/ranting, but you can
> actually use gnome-software on the command line.
> /usr/libexec/gnome-software-cmd (no GTK parts get loaded) has got a
> bit cleverer in F26 and is set to get even cleverer in F27. With this
> tool you can install/remove/update flatpaks, packages, gnome shell
> extensions, and even update firmware. It's not quite ready for human
> consumption (it's designed as a debug tool), but it could quite easily
> be moved into /usr/bin/ and a man page be written. I don't think
> "teach dnf about everything" is a super practical plan.
I dunno about "practical", but "one unified commandline tool to manage
all the software on my system" sure is *nice* from a user and admin
perspective. Maybe the dnf tool could be a plugin wrapper around
Please not, package manager is our way to distribute the software and
thus should never be coupled to any specific upstream projects which
could have a different view on things, make changes etc. and we have a
"possibility" of a broken package management. It has to work the other
way around, a plugin for DNF would be the solution for that. So a plugin
which can query gnome-software-cmd to get access to these additional
resources, but if anything is messed up, disable plugin → core package
management works again.