summaryrefslogtreecommitdiff
path: root/contrib/bash_completion
diff options
context:
space:
mode:
authorNagy Gabor <ngaba@bibl.u-szeged.hu>2009-09-15 12:30:32 +0200
committerDan McGee <dan@archlinux.org>2009-09-20 12:01:25 -0500
commitef3716877032941f7882c11c5a091abef95ef983 (patch)
treed67e75fb6c9c29a2252d44cc32b04310cdd51fa6 /contrib/bash_completion
parent481014e944731e2756e16a7283f8a10498cadba4 (diff)
downloadpacman-ef3716877032941f7882c11c5a091abef95ef983.tar.xz
Ask user confirmation for -R operation, too
After commit 0da96abc, pacman always asks user confirmation for -U, so it is more coherent to doing that for -R, too. Btw, most users use -Rs always, so they won't notice any change. In the old code the -Ru operation was forgotten: Though it is a not "dangerous" operation, but the target list can be changed by that, too. Non-interactive scripts should always use --noconfirm (unexpected questions can be asked by all transactions). [That's why we should always default to the safest answers.] I've also added a pkglist != NULL sanity check (because -Ru can empty target list in trans_prepare part). Signed-off-by: Nagy Gabor <ngaba@bibl.u-szeged.hu> Signed-off-by: Dan McGee <dan@archlinux.org>
Diffstat (limited to 'contrib/bash_completion')
0 files changed, 0 insertions, 0 deletions