Re: GIT_EXEC_PATH

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue, Apr 18, 2017 at 01:47:14PM +0200, Christoph Egger wrote:
> 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@xxxxxxxxxxxxxx/

Kevin



[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]