Re: git's directory is _prepended_ to PATH when called with an absolute path

2015-04-22 Thread David Rodríguez
On 22/04/15 14:02, brian m. carlson wrote: "I want whatever ruby the user chooses." This is exactly what I want. The problem is that git overrides the user's choice by prepending /usr/bin to the path and thus making /usr/bin/env choose system's ruby version. Which is almost always not the Ruby

Re: git's directory is _prepended_ to PATH when called with an absolute path

2015-04-22 Thread brian m. carlson
On Wed, Apr 22, 2015 at 05:31:09PM +0200, Andreas Krey wrote: > On Wed, 22 Apr 2015 08:36:00 +, David Rodríguez wrote: > ... > > * User is relying on a custom path to select their Ruby version. For > > example, let's say the first folder in path is "~/.rubies/2.2.2/bin". > > * User runs "/usr/b

Re: git's directory is _prepended_ to PATH when called with an absolute path

2015-04-22 Thread Andreas Krey
On Wed, 22 Apr 2015 08:36:00 +, David Rodríguez wrote: ... > * User is relying on a custom path to select their Ruby version. For > example, let's say the first folder in path is "~/.rubies/2.2.2/bin". > * User runs "/usr/bin/git commit" and a pre-commit hook is triggered. > * The pre-commit h

Re: git's directory is _prepended_ to PATH when called with an absolute path

2015-04-22 Thread David Rodríguez
On 22/04/15 02:47, Andreas Krey wrote: On Tue, 21 Apr 2015 18:37:29 +, David Rodríguez wrote: ... This causes issues with Ruby git hooks, because Ruby version managers rely on custom settings in PATH to select the Ruby executable, Even if git wouldn't modify PATH this is still a broken way

Re: git's directory is _prepended_ to PATH when called with an absolute path

2015-04-21 Thread Andreas Krey
On Tue, 21 Apr 2015 18:37:29 +, David Rodríguez wrote: ... > This causes issues with Ruby git hooks, because Ruby version managers > rely on custom settings in PATH to select the Ruby executable, Even if git wouldn't modify PATH this is still a broken way to do that. What ruby to execute a ho

Re: git's directory is _prepended_ to PATH when called with an absolute path

2015-04-21 Thread David Rodríguez
I'm actually not sure how to reply to an old thread... From the thread I gather that the intention is to prevent this behavior and stop prepending git's directory to the path. Is that right? On 21/04/15 18:59, David Rodríguez wrote: Thanks Junio for the useful link, I'll comment there. On 21

Re: git's directory is _prepended_ to PATH when called with an absolute path

2015-04-21 Thread David Rodríguez
Thanks Junio for the useful link, I'll comment there. On 21/04/15 18:48, Junio C Hamano wrote: http://thread.gmane.org/gmane.comp.version-control.git/267143/focus=267251 -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More

Re: git's directory is _prepended_ to PATH when called with an absolute path

2015-04-21 Thread Junio C Hamano
http://thread.gmane.org/gmane.comp.version-control.git/267143/focus=267251 -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html

git's directory is _prepended_ to PATH when called with an absolute path

2015-04-21 Thread David Rodríguez
For example, if I run git using: $ /usr/bin/git then /usr/bin is prepended to the path. Is this intentional? If it is, why? This causes issues with Ruby git hooks, because Ruby version managers rely on custom settings in PATH to select the Ruby executable, and there's usually a system Ruby li