[pacman-dev] [PATCH] libalpm/sync.c: restrict alpm_sync_newversion by USAGE_UPGRADE

Eli Schwartz eschwartz at archlinux.org
Wed Jul 25 03:51:50 UTC 2018

On 07/24/2018 02:48 PM, 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
> 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 don't really see the utility... a search-only database will not show
the upgrades in pacman -Su (even ignored packages get shown, just as a
warning instead of an active transaction member).

pacman -Qu should therefore (IMHO) only show those Sync packages (with
[ignored] in cases, yes).

When people hear about -Qu, they generally hear about it as "oh, the
thing which is like -Su except it doesn't actually do the thing".

Admittedly the actual thing which doesn't actually do the thing would be
pacman -Sup --print-format '%r/%n %v'

But then we're faced with the classic problem "print-format? no such
thing, we don't support that and you should use expac, HAHAHAHA, oh wait
print-format is actually useful here (surprise!)"

So actually I guess in theory it's completely different, but now I'm not
sure what I would specifically use this behavior for.

Eli Schwartz
Bug Wrangler and Trusted User

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <https://lists.archlinux.org/pipermail/pacman-dev/attachments/20180724/92f585ef/attachment.asc>

More information about the pacman-dev mailing list