From: Matthew Ogilvie <mmogilvi_git@miniinfo.net>
To: git@vger.kernel.org, gitster@pobox.com
Cc: Matthew Ogilvie <mmogilvi_git@miniinfo.net>
Subject: [PATCH v2 6/6] INSTALL: document a simpler way to run uninstalled builds
Date: Sun, 29 Nov 2009 23:19:31 -0700 [thread overview]
Message-ID: <1259561971-25730-7-git-send-email-mmogilvi_git@miniinfo.net> (raw)
In-Reply-To: <1259561971-25730-6-git-send-email-mmogilvi_git@miniinfo.net>
The new scripts automatically saved in the bin-wrappers
directory allow you test run a build when you have neither installed
git nor tweaked environment variables. Mention this in INSTALL,
along with the slight performance issue of doing so.
This can be especially handy for manually testing
network-invoked git (from ssh, web servers, or similar), but
it is also handy with a plain command prompt.
Signed-off-by: Matthew Ogilvie <mmogilvi_git@miniinfo.net>
---
INSTALL | 14 +++++++++++++-
1 files changed, 13 insertions(+), 1 deletions(-)
diff --git a/INSTALL b/INSTALL
index be504c9..ee718c6 100644
--- a/INSTALL
+++ b/INSTALL
@@ -39,7 +39,19 @@ Issues of note:
with --disable-transition option to avoid this.
- You can use git after building but without installing if you
- wanted to. Various git commands need to find other git
+ want to.
+
+ The simplest option for running some manual tests of a build
+ before installing it is to use the wrapper scripts that are built
+ and saved into `pwd`/bin-wrappers. Either invoke the scripts in
+ bin-wrappers using their full paths, put bin-wrappers in your
+ PATH, or copy/symlink just the bin-wrappers scripts into somewhere
+ already in your PATH. But this option is slightly inefficient,
+ so for a more permanent solution we recommend either installing
+ git (you can set a prefix to install right next to your
+ build directory), or use the alternative below.
+
+ Alternatively, various git commands need to find other git
commands and scripts to do their work, so you would need to
arrange a few environment variables to tell them that their
friends will be found in your built source area instead of at
--
1.6.4.GIT
next prev parent reply other threads:[~2009-11-30 6:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-30 6:19 [PATCH v2 0/6] Run test suite without dashed commands in PATH Matthew Ogilvie
2009-11-30 6:19 ` [PATCH v2 1/6] t2300: use documented technique to invoke git-sh-setup Matthew Ogilvie
2009-11-30 6:19 ` [PATCH v2 2/6] t3409 t4107 t7406: use dashless commands Matthew Ogilvie
2009-11-30 6:19 ` [PATCH v2 3/6] t/README: Document GIT_TEST_INSTALLED and GIT_TEST_EXEC_PATH Matthew Ogilvie
2009-11-30 6:19 ` [PATCH v2 4/6] build dashless "bin-wrappers" directory similar to installed bindir Matthew Ogilvie
2009-11-30 6:19 ` [PATCH v2 5/6] run test suite without dashed git-commands in PATH Matthew Ogilvie
2009-11-30 6:19 ` Matthew Ogilvie [this message]
2009-11-30 6:48 ` [PATCH v2 6/6] INSTALL: document a simpler way to run uninstalled builds Junio C Hamano
2009-12-01 17:24 ` [PATCH v2 5/6] run test suite without dashed git-commands in PATH Jakub Narebski
2009-12-02 5:49 ` Matthew Ogilvie
2009-12-02 6:25 ` Junio C Hamano
2009-11-30 6:28 ` [PATCH v2 4/6] build dashless "bin-wrappers" directory similar to installed bindir Junio C Hamano
2009-12-01 7:33 ` Matthew Ogilvie
2009-11-30 7:16 ` [PATCH v2 0/6] Run test suite without dashed commands in PATH 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=1259561971-25730-7-git-send-email-mmogilvi_git@miniinfo.net \
--to=mmogilvi_git@miniinfo.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/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).