From: Junio C Hamano <gitster@pobox.com>
To: Christian Hesse <mail@eworm.de>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 1/3] create gpg homedir on the fly
Date: Fri, 12 Dec 2014 12:33:43 -0800 [thread overview]
Message-ID: <xmqqk31wbobc.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <1418374214-8241-1-git-send-email-mail@eworm.de> (Christian Hesse's message of "Fri, 12 Dec 2014 09:50:12 +0100")
After queuing these three, I _think_ it is better to have something
like this patch on top, as it is distracting to let the GPG message
while setting up the test gpghome leak into the test output,
especially without running these tests with "-v" option.
The splitting of RFC1991 prerequiste part is about future-proofing.
When we want to define other kinds of specific prerequisites in the
future, I'd prefer to see it done separately from the basic set-up
code.
t/lib-gpg.sh | 26 ++++++++++++++------------
1 file changed, 14 insertions(+), 12 deletions(-)
diff --git a/t/lib-gpg.sh b/t/lib-gpg.sh
index b611b78..33de402 100755
--- a/t/lib-gpg.sh
+++ b/t/lib-gpg.sh
@@ -16,23 +16,25 @@ else
# Type DSA and Elgamal, size 2048 bits, no expiration date.
# Name and email: C O Mitter <committer@example.com>
# No password given, to enable non-interactive operation.
- mkdir ./gpghome
- chmod 0700 ./gpghome
- GNUPGHOME="$(pwd)/gpghome"
- export GNUPGHOME
- gpg --homedir "${GNUPGHOME}" --import \
- "$TEST_DIRECTORY"/lib-gpg/keyring.gpg
- gpg --homedir "${GNUPGHOME}" --import-ownertrust \
- "$TEST_DIRECTORY"/lib-gpg/ownertrust
+ mkdir ./gpghome &&
+ chmod 0700 ./gpghome &&
+ GNUPGHOME="$(pwd)/gpghome" &&
+ export GNUPGHOME &&
+ gpg --homedir "${GNUPGHOME}" 2>/dev/null --import \
+ "$TEST_DIRECTORY"/lib-gpg/keyring.gpg &&
+ gpg --homedir "${GNUPGHOME}" 2>/dev/null --import-ownertrust \
+ "$TEST_DIRECTORY"/lib-gpg/ownertrust &&
test_set_prereq GPG
- if echo | gpg --homedir "${GNUPGHOME}" -b --rfc1991 >/dev/null 2>&1
- then
- test_set_prereq RFC1991
- fi
;;
esac
fi
+if test_have_prereq GPG &&
+ echo | gpg --homedir "${GNUPGHOME}" -b --rfc1991 >/dev/null 2>&1
+then
+ test_set_prereq RFC1991
+fi
+
sanitize_pgp() {
perl -ne '
/^-----END PGP/ and $in_pgp = 0;
next prev parent reply other threads:[~2014-12-12 20:33 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-11 13:16 [PATCH v2 1/1] create gpg homedir on the fly and skip RFC1991 tests for gnupg 2.1 Christian Hesse
2014-12-11 22:41 ` Junio C Hamano
2014-12-12 8:47 ` Christian Hesse
2014-12-12 8:50 ` [PATCH 1/3] create gpg homedir on the fly Christian Hesse
2014-12-12 8:50 ` [PATCH 2/3] skip RFC1991 tests for gnupg 2.1 Christian Hesse
2014-12-12 8:50 ` [PATCH 3/3] replace binary keyrings with armored keys Christian Hesse
2014-12-12 18:36 ` Junio C Hamano
2014-12-12 20:42 ` Christian Hesse
2014-12-12 21:50 ` Junio C Hamano
2014-12-13 19:30 ` Christian Hesse
2014-12-12 8:52 ` [PATCH 1/3] create gpg homedir on the fly Eric Sunshine
2014-12-12 8:55 ` Christian Hesse
2014-12-12 18:26 ` Junio C Hamano
2014-12-12 20:33 ` Junio C Hamano [this message]
2014-12-12 20:45 ` Christian Hesse
2014-12-12 20:33 ` Junio C Hamano
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqk31wbobc.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=mail@eworm.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).