jacogr
El Capitan SIP feature breaks git flow
The new System Integrity Protection feature in OSX El Capitan prevents a user from modifying /usr/bin, even with sudo. That means that the git flow integration breaks since symbolic links cannot be created according to the instructions in the readme.
A possible solution would be to execute git flow operations via their actual path, /usr/local/bin/git-flow.
This would of course mean that git-promise needs to update their package to allow calls with another git than the one in $PATH.
I have a PR ready and can raise the issue with the @piuccio from git-promise. I just want to make sure that this is something you would accept.
I'm ok to change git-promise if needed.
git function already accepts an options object, at the moment it only handles cwd but it can be used to pass a different git path
Looks like a good change to me, I want to push out a new version of git-control by the end of next week. If the PR / change to git-promise happens before that, then I will merge and include it :)
I'm not sure I have lot of time on my side to change git-promise, but if someone comes up with a PR I'll review.
@MarcelMue I pulled in @piuccio new changes for override git and added gitExec to git.coffee but git-flow still does not function. All git commands use the git I am pointing to, but when I execute git flow from git-control I get a 'PATH/TO/git flow -d' is not a git command error 1
The only "git flow" command that should be called with "-d" parameter, is "git flow init -d". "git flow -d" is not a valid command itself, and should return the "man page" for git flow. but the "is not a git command" seems to be a sign of your script pointing to a git binary without git-flow extensions. How did you install git-flow-avh ? Is it functional in the terminal?
