On Tue, 2017-02-28 at 08:50 -0800, Adam Williamson wrote:
Bodhi 2.x:
1. bodhi updates download --updateid (updateid)
2a. dnf update *.rpm
2b. dnf install *.rpm
You could in theory improve on this a bit for the 'update' case by
only
downloading packages that would actually be involved in an update -
this would be a substantial help in a few cases, where there are
hundreds of subpackages in the update but you only need one or two.
However, this does get tricky because of renames: you can't just
download only packages that are already installed, you have to
consider
packages that obsolete existing installed packages.
Yeah I do this when it's a large update (like KDE) now. That's what
made me think of this feature actually - I wanted to try a new KDE
update and it was a bit of a pain to avoid installing RPMs that weren't
already installed on my system, while still installing RPMs that were
actually new dependencies. I ended up making a crazy shell thing with
lots of grepping and pipes to sort it out in my case (because I didn't
want every KDE package, just the ones I use). I think it could be cool
to be able to be able to do something like this:
$ dnf bodhi_update FEDORA-2017-blahblahblah
and have it do "the right thing". We could also give a bodhi_install
that does install all of them for testers who prefer that behavior. Or
maybe there are better names. Or we could just give this feature to the
bodhi CLI itself, something like:
$ bodhi updates install --updateid (updateid)
$ bodhi updates upgrade --updateid (updateid)
I put a todo in task warrior to look into doing this myself, but it's
sitting pretty low on the list compared to my other tasks ☺