From: Junio C Hamano <gitster@pobox.com>
To: Michael J Gruber <git@drmicha.warpmail.net>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 2/2] test-lib.sh: Allow running the test suite against installed git
Date: Sat, 14 Mar 2009 13:25:35 -0700 [thread overview]
Message-ID: <7v3adfc0n4.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <1236959116-3334-3-git-send-email-git@drmicha.warpmail.net> (Michael J. Gruber's message of "Fri, 13 Mar 2009 16:45:16 +0100")
Michael J Gruber <git@drmicha.warpmail.net> writes:
> Introduce variables externalpath and externalexecpath such that the test
> suite can be run against a git which is installed at $externalpath with
> subcommands at $externalexecpath. externalpath defaults to the git.git
> checkout, externalexecpath defaults to $externalpath. Run the suite as
>
> externalpath=somepath externalexecpath=someotherpath make test
>
> but note that this requires and uses parts of a compiled git in the
> git.git checkout: test helpers, templates and perl libraries are taken
> from there.
While I like the end result this series tries to achieve, may I suggest a
few things?
- This is like GIT_SKIP_TESTS and GIT_TEST_HTTPD in that extra
environments affect how the tests are run. It would be much easier to
use if the new environment variables are named similarly, prefixed with
GIT_, in all caps, and with underscores between words.
- When externalpath is given but not externalexecpath, you can deduce the
latter from the former by running "$externalpath/git --exec-path",
which makes running the tests against an installed git even easier.
For example, I keep many git installations under $HOME/git-snap-vX.Y.Z,
and it would be great if your patch allowed me to say something like:
$ GIT_TEST_INSTALLED=$HOME/git-snap-v1.4.4.4/bin/git make test
next prev parent reply other threads:[~2009-03-14 20:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-13 15:45 [PATCH 0/2] Allow running the test suite against installed git Michael J Gruber
2009-03-13 15:45 ` [PATCH 1/2] test-lib.sh: Test for presence of git-init in the right path Michael J Gruber
2009-03-13 15:45 ` [PATCH 2/2] test-lib.sh: Allow running the test suite against installed git Michael J Gruber
2009-03-14 20:25 ` Junio C Hamano [this message]
2009-03-16 17:03 ` [PATCHv2 0/2] " Michael J Gruber
2009-03-16 17:03 ` [PATCHv2 1/2] test-lib.sh: Test for presence of git-init in the right path Michael J Gruber
2009-03-16 17:03 ` [PATCHv2 2/2] test-lib.sh: Allow running the test suite against installed git Michael J Gruber
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=7v3adfc0n4.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@drmicha.warpmail.net \
--cc=git@vger.kernel.org \
/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).