Browse Source

Use GIT_EXEC_PATH explicitly for initial git-init-db in tests.

This is just a belts-and-suspenders check, but makes sure we
have both "git" and "git-init-db" built, executable, and
checking.

Signed-off-by: Junio C Hamano <junkio@cox.net>
maint
Junio C Hamano 19 years ago
parent
commit
10b94e283a
  1. 5
      t/test-lib.sh

5
t/test-lib.sh

@ -149,7 +149,7 @@ test_expect_code () {
test_done () { test_done () {
trap - exit trap - exit
case "$test_failure" in case "$test_failure" in
0) 0)
# We could: # We could:
# cd .. && rm -fr trash # cd .. && rm -fr trash
# but that means we forbid any tests that use their own # but that means we forbid any tests that use their own
@ -190,8 +190,7 @@ test=trash
rm -fr "$test" rm -fr "$test"
mkdir "$test" mkdir "$test"
cd "$test" cd "$test"
git init-db --template=../../templates/blt/ 2>/dev/null || "$GIT_EXEC_PATH/git" init-db --template=../../templates/blt/ 2>/dev/null ||
error "cannot run git init-db" error "cannot run git init-db"


mv .git/hooks .git/hooks-disabled mv .git/hooks .git/hooks-disabled


Loading…
Cancel
Save