summaryrefslogtreecommitdiffstats
path: root/lib/libalpm/po
diff options
context:
space:
mode:
authorAllan McRae <allan@archlinux.org>2019-01-10 04:44:32 +0100
committerAllan McRae <allan@archlinux.org>2019-01-10 05:14:04 +0100
commite9d91a688d1a2ebe58e8a895853debf745a529cf (patch)
tree8b0cf8ee5159de8ce596df62140dfda941bd6e61 /lib/libalpm/po
parent9b2a90cfb1910b5092ffec3375177229101323e4 (diff)
downloadpacman-e9d91a688d1a2ebe58e8a895853debf745a529cf.tar.gz
pacman-e9d91a688d1a2ebe58e8a895853debf745a529cf.tar.xz
libalpm/sync.c: change alpm_sync_newversion() to alpm_sync_get_new_version()
The behaviour of "pacman -Qu" was very strange... It would only consider packages from repos with Usage = Search (or All), and ignore those with Usage = Sync, Install or Upgrade. This is because the function alpm_sync_newversion() used ALPM_DB_USAGE_SEARCH for its filtering. Given this function is documented (at least in the source) to "Check for new version of pkg in sync repos", I would expect that to look at all repos. However, just changing this parameter, would result in a fairly silent change in behaviour of this function. Instead, rename the function and remove this filtering altogether. Users of this function can filter the dbs passed to this function to achieve their desired output. Signed-off-by: Allan McRae <allan@archlinux.org>
Diffstat (limited to 'lib/libalpm/po')
0 files changed, 0 insertions, 0 deletions