Stefan Beller <sbeller@xxxxxxxxxx> writes:
> On Mon, Nov 7, 2016 at 10:30 AM, Anthony Sottile <asottile@xxxxxxxxx> wrote:
>> This has worked great up until now (and is very convenient for trying things
>> out without blowing away the system installation). What changed?
>>
>
> (Just guessing myself:)
>
> $ git log --grep git-sh-i18n v2.10.0..v2.11.0-rc0
> ...
> commit 1073094f30a8dd5ae49f2146f587085c4fe86410
> Author: Anders Kaseorg <andersk@xxxxxxx>
> Date: Sat Oct 29 22:10:02 2016 -0400
>
> git-sh-setup: be explicit where to dot-source git-sh-i18n from.
>
> d323c6b641 ("i18n: git-sh-setup.sh: mark strings for translation",
> 2016-06-17) started to dot-source git-sh-i18n shell script library,
> assuming that $PATH is already adjusted for our scripts, namely,
> $GIT_EXEC_PATH is at the beginning of $PATH.
> ...
Before that one since v2.10.0, there ie d323c6b641 that starts to
include git-sh-i18n from git-sh-setup in the first place. If you are
testing or using a newly-out-of-oven uninstalled Git, you would need
to do these to be correctly using it:
* Many subcommand executables and helpers are not installed on any
directory on your $PATH, but are installed in GIT_EXEC_PATH.
Find out where it is by asking the newly-out-of-oven Git "git
--exec-path" without setting GIT_EXEC_PATH environment variable.
That is where your newly built one wants to find things.
* Because you are trying to use the newly-out-of-oven Git without
installing, you do not want to install into the real
GIT_EXEC_PATH location yet. Pick a new empty directory and
arrange the files that would be installed by our Makefile into
"git --exec-path" if you did "make install" to be in this new
location. The set of files include git-sh-setup and git-sh-i18n.
* Set and export GIT_EXEC_PATH to point at this new empty directory
you just populated.
That incidentally is how we make our "make test" work.
If you only set $PATH to the top of git build directory, without
doing the above arrangement with GIT_EXEC_PATH, things may have
appeared to work due to multitude of accidents. Builtin commands
would worked fine because it is just a single "git" binary after
all, i.e. "git log" would not have consulted a "git-log" binary on
anywhere in your filesystem. Other commands may have been run from
the already installed version on the system. The latter is
particularly problematic, because it means that one thought that one
is testing the newly built on before installing to make sure that
the new one works OK, but is actually testing the already installed
one.