On 2020-09-26 22:32:25+0200, Johannes Schindelin <Johannes.Schindelin@xxxxxx> wrote: > > Since the Git-for-windows installer does append > > 'your_installation_directory'/Git/bin to the PATH variable, it should > > be fine. > > No, it does not. Quite purposefully so. > > The `/bin/` directory is kind of a hack to reinstate _some_ level of > support for use cases that relied on Git for Windows v1.x installing its > binaries into that directory (v2.x distributes them between `/usr/bin/` > and `/mingw64/bin/`). > > What _does_ get appended, at least by default, is the `/cmd/` directory > (which does _not_ contain `sh.exe`). > > Now, there _is_ an option in the Git for Windows installer to append all > of its Unix tools to the `PATH`, but it is highly discouraged to do so. I agree with this decision. > > > I personally don't install my dev tools(except Visual Studio) to > > Program Files(because of the _space_), it messes up the Makefiles. > > Sure, and that's your prerogative. There's unfortunately no good way to > support your use case. > > Luckily, the vast majority of Git for Windows' users do not change the > default location, and this patch is for them. (And "them" in this case > includes me, personally ;-)) This doesn't fit into my view of Git for Windows' users For some users that have the Administrator right, it's the default location if they grant the Administrator right for the installer. For those poor souls that works for enterprise companies, and thoses that not feel comfortable give Administrator right to _another_ installer, the installer will install into (hopeful, I type it right): %USERPROFILE%/AppData/Local/Programs/Git I think it's better to offer SH_EXE as an OPTION, let user specify it as will. And we'll search in PATH if it's not specified, fallback to 2 default value if not found. -- Danh
