They get started in the background and stay around which comes with various problems:
* The files can't be deleted until they are stopped
* Some CI systems wait until all programs are stopped
* On a cygwin update we have to restart everything or forking will be broken
(though pacman takes care of that now by killing everything cygwin-like on a core update)
Ideally though they would just exit in a controlled way after we no longer need them.
The reason this uses GNUPGHOME instead of passing --home to gpgconf is that dirmngr started by
"pacman-key --refresh-keys" somehow couldn't be killed that way.
Maybe because gpg doesn't forward --homedir in that case. Setting GNUPGHOME helped.
It is all fine and dandy when users GPG-sign files from the terminal.
But when they do not, things get more complicated.
The usual thing is to install a pinentry helper targeting your graphical
desktop and then launching the GPG agent somehow and connet it all
together.
Except that MSYS2 does not come with a gpg-agent.
So let's just imitate openssh, which interprets the environment variable
SSH_ASKPASS (if set) as the path to a helper that can be called upon to
ask the user to provide a passphrase.
Unsurprisingly, the new environment variable is called GPG_ASKPASS (and
we do not repeat Git's mistake of co-opting SSH_ASKPASS, if set).
This allows, say, Git for Windows' Git GUI to commit with GPG signatures
even if the passphrase is not empty.
Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
* upgrade some broken packages
* correct some broken urls/checksums
* use secure urls where possible
* use stable url for ncurses
* some whitespace fixes
Remaining md5sums either didn't download or
didn't pass checksum tests.
