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@xxxxxxxxxxxx>
---
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
--
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