[arch-general] pacman "Targets" sort order

[David C. Rankin]

Guys,

   I don't know if I am remembering correctly, but I thought the upgrade 
"Targets" were sorted alphabetically by name prior to the pacman upgrade a 
month or two ago. Now, it looks like they are listed either by repository, 
then alphabetized or some other logic that ends up -- almost alphabetized. 
Specifically:

Targets (35): bluez-4.93-1  run-parts-3.4.4-1  ca-certificates-20110421-3
               dcron-4.5-2  libzip-0.10-1 ebook-tools-0.2.1-2  eina-svn-
               58920-1  eet-svn-58955-1  evas-svn-58958-1  ecore-svn-58945-1
               e_dbus-svn-58954-1  embryo-svn-58829-1  edje-svn-58887-1
               pciutils-3.1.7-4  udev-167-2 eeze-svn-58668-1  efreet-
               svn-58672-1  e-svn-58940-1  gutenprint-5.2.7-1  hdf5-1.8.6-1
               libidn-1.21-1  libxcb-1.7-2  networkmanager-0.8.999-1  openssh-
               5.8p2-1  python2-cairo-1.10.0-1 python2-distribute-0.6.16-1
               qt-4.7.3-1  rp-pppoe-3.10-6  sudo-1.8.1.p1-1  telepathy-
               qt4-0.5.16-1 zziplib-0.13.60-1  texlive-bin-2010.1-8  texlive-
               core-2010.22154-1  udev-compat-167-2 usbutils-002-2

bluez -> run-parts -> ca-certificates??

   In the past, I would scan the list to make sure there were no updates that 
I didn't want or that I needed to put off due to bugs or what not. Now I've 
been bitten a time or two by searching through long Target lists and 
confirming there were no unwanted updates only to find out that an unwanted 
update was alphabetized higher-up or lower in the target list.

   Has the target list always sorted by repo, then by name --or-- was the list 
fully sorted by name earlier? If so, is it easy to change?

   In short lists, it's not really a big deal, but when you have over 100 
targets, having them sorted by name really helps. What say the pacman gurus?

-- 
David C. Rankin, J.D.,P.E.