summaryrefslogtreecommitdiffstats
path: root/scripts/pacman-db-upgrade.sh.in
diff options
context:
space:
mode:
authorDenis A. AltoƩ Falqueto <denisfalqueto@gmail.com>2010-10-08 02:13:13 +0200
committerDan McGee <dan@archlinux.org>2011-03-23 07:59:42 +0100
commit422925a65efb2abcc6a3cac34f09de2dbf8664be (patch)
tree709dbf5cceb2b06106a2b4e86302e334d90c4dd1 /scripts/pacman-db-upgrade.sh.in
parentae20f8820278d285400afb7c3b7f2ba3c789c61a (diff)
downloadpacman-422925a65efb2abcc6a3cac34f09de2dbf8664be.tar.gz
pacman-422925a65efb2abcc6a3cac34f09de2dbf8664be.tar.xz
pacman-key: remake of --reload command
The --reload command was refactored to allow a more flexible management. There are two sets of keys that will be added, one that will be removed and one that will be kept. The set of keys to be kept are configured in pacman.conf, with the option HoldKeys, with the same meaning of HoldPkgs. It can be repeated and several values can be put in the same entry. The new behavior allows a key to be marked for removal, but the user can decide if that key must be kept. For example, if a developer has a public repository, signed with his own key, that key must be added to the HoldKeys option. If the key is marked for removal from pacman's keyring, it will not be removed for the users that have configured HoldKeys correctly. There are other minor fixes, mainly in the handling of --add command when there is no aditional parameter. In that case, pacman-key will behave just like gpg, adding the contents of stdin into pacman's keyring. Signed-off-by: Denis A. AltoƩ Falqueto <denisfalqueto@gmail.com>
Diffstat (limited to 'scripts/pacman-db-upgrade.sh.in')
0 files changed, 0 insertions, 0 deletions