Part 1 corrects only an inconsistency which does not matter as long as you run tests against git compiled in a checkout only: There, $GIT_EXEC_PATH contains git, in general it does not. Part 2 allows running the test suite against a git installed anywhere in the file system. This has at least 2 use cases: - Test an installed distro package after the installation. - Run easily current tests against older versions, or vice versa, if you have those versions installed somewhere. Note that one still needs git compiled in git.git for test helpers etc., and also because I did not adjust the paths to templates and such. I did not really feel a need for that. Also, in t0000 there is still one explicit use of "../git" which is fine because it simply tests for the presence of a build, which we need anyways. v2 incorporates feed-back by JCH: variables are named GIT_TEST_INSTALLED and GIT_TEST_EXEC_PATH now, the latter defaulting to the output of $GIT_TEST_INSTALLED/git --exec-path. Also, we exit gracefully in case we cannot run $GIT_TEST_INSTALLED/git. Michael J Gruber (2): test-lib.sh: Test for presence of git-init in the right path. test-lib.sh: Allow running the test suite against installed git t/test-lib.sh | 14 +++++++++++--- 1 files changed, 11 insertions(+), 3 deletions(-) -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
