Re: GIT_EXEC_PATH
- From
Kevin Daudt <me@ikke.info>
- Date
- Apr 18, 2017, 16:49 UTC
- Message-ID
- <20170418164917.GA24697@alpha.ikke.info>
- In-Reply-To
- <A351EA5C-734D-4833-821F-1B5AA49895BF@cs.fau.de>
On Tue, Apr 18, 2017 at 01:47:14PM +0200, Christoph Egger wrote:
Show 8 quoted lines
> Hi! > > Concerning $GIT_EXEC_PATH .. is that supposed to be a $PATh like variable? as in can it have more than one path (colon-separated)? I have currently two directories there (one with a git-annex installation, one with the normal git stuff) and it seems to mostly work. However git-sh-setup is unhappy: > > > % git pull --rebase > > /opt/local/libexec/git-core/git-sh-setup: line 46: /opt/local/libexec/git-core:/Applications/git-annex.app/Contents/MacOS//git-sh-i18n: No such file or directory > > Christoph
Hello Chistoph,
The exec path is not just $PATH, it should just point to a single directory.
See [1] for a recent thread about this:
Junio C Hamano wrote:
> That environment variable is designed to hold a single path, not > like $PATH that lists multiple places in a colon separated list.
https://public-inbox.org/git/CAJF7t-dqSa7tmQqNEWmg_VZ=+832nsZ-3JmSGA03qK6aY5eNTQ@mail.gmail.com/
Kevin