[pacman-dev] additional (small) pacman issues

[Scott Horowitz]

I've been somewhat systematically going through the various less
commonly used options, and there are some issues. Most of these are
smaller than the ones James has previously described ;)

1. pacman -S --noprogressbar seems to add some extra "done"s  and is
missing some other output like (1/2) next to the installed package.
Note the differences here between pacman -S and pacman -S
--noprogressbar:

noprogressbar:
checking package integrity... done.
cleaning up... done.
checking for file conflicts... done.
installing libmpd... done.
done.
installing gimmix... done.
done.

progressbar:
checking package integrity... done.
cleaning up... done.
(2/2) checking for file conflicts
[###############################] 100%
(1/2) installing libmpd
[###############################] 100%
(2/2) installing gimmix
[###############################] 100%

pacman -R --noprogressbar also strips the (1/1) parts.

2. pacman -S --noscriptlet -> should this be a permanent action? In
other words, if I pacman -S --notscriptlet foo and then pacman -S foo
(or pacman -Su when foo is updated), should the script run the second
time? I can understand it working either way: 1) if you install with
noscriptlet, you never want the script to run, or 2) if you pacman -S
a second time without specifying noscriptlet, you'd want the script to
run. The docs aren't explicit enough for me to understand. Maybe -S/U
foo should be handled differently than pacman -Su.

3. How does pacman -Qc work? I've tried it on numerous packages and
have to find one with a changelog displayed by pacman.

4. The following are missing from the man page: --noscriptlet, --ask, -Qc, -Se

5. "--noconfirm      do not ask for anything confirmation" -> that
should probably read "do not ask for any confirmation"

Scott