No way to get Unix tools on the Path using the installer via the command-line

[MathiasMagnus]

The issue is that virtually none of the package managers on Windows seem to be able to add the Unix utilities to the PATH. Chocolatey's manifests as well as dozens of GitHub search hits refer to /GitAndUnixToolsOnPath which is absent from both the documentation and the actual code that seems to create the installer.

No matter if one specifies the probably legacy /GitAndUnixToolsOnPath or /PathOption=CmdTools which seems like the more current method: The installation doesn't reflect either of these flags, nor does it if one tries throwing in /TASKS=modpath_all. All of this using the latest installer at the time of writing, 2.49 (x64).

Is it user error or is the installer really borked?

[rimrul]

You want /o:PathOption=CmdTools

[MathiasMagnus]

@rimrul Wow, thanks. That does the trick. How did we miss this from the docs? There's an entire page on all the types of args, but there's nothing on how to actually pass them. Maybe some sign posting is warranted. Feel free to close the issue or repurpose as a doc ticket.

[dscho]

@MathiasMagnus there is some documentation at https://gitforwindows.org/mapping-between-git-installer-gui-settings-and-command-line-arguments.html (not sure how up to date it is).

[MathiasMagnus]

That looks about right, but there's no mention of /o: to pass all these options on the CLI. And given how all of the package managers get this wrong, Git for Windows may want to throw a bone: maybe by erroring out when unknown command-line options are given. (Just an idea)

[dscho]

@MathiasMagnus you can fix the lack of /o: mention by opening a PR changing https://github.com/git-for-windows/git-for-windows.github.io/blob/HEAD/content/mapping-between-git-installer-gui-settings-and-command-line-arguments.md, and you can propose the change in the installer by opening a PR changing https://github.com/git-for-windows/build-extra/blob/HEAD/installer/install.iss.