On 8/29/18 12:30 AM, Allan McRae wrote: > On 25/07/18 04:48, Dave Reisner wrote: >> On Tue, Jul 24, 2018 at 05:53:00PM +0100, morganamilo wrote: >>> Commit 106d0fc54 Added the usage option for databases and >>> alpm_sync_newversion was restricted by USAGE_SEARCH instead of >>> USAGE_UPGRADE. >> I don't recall exactly what my thinking was when I wrote this patch, but >> looking at 'pacman -Qu' output right now, I think I actually I like >> seeing potential upgrades, not just "actual" upgrades. >> >> Anyone else have an opinion? >> > > I just spent some time looking into this... only a month after submission! > > My thoughts: > > 1) Implementing --print-format usage for -Su is the correct way to > determine updates. (I guess in combination with --no-confirm?)
It works today, though, as I mentioned above. The only "problem" is that people never remember --print-format exists, mostly because it's not implemented in all the *other* cases where we'd want to have it. > 2) -Qu should label those package updates that are available but won't > be updated by -Su due to database restriction. We currently do this for > packages in IgnorePkg, so should be an "easy" extension. > > Would that be suitable for everyone? That sounds like something very nice to have, yes. -- Eli Schwartz Bug Wrangler and Trusted User
signature.asc
Description: OpenPGP digital signature
