Why doesn't cli use the version of dotnet-install in repo?

This is probably a stupid question, so apologies in advance.

Why does the cli grab the dotnet-install.sh script from github rather than using the copy at scripts/obtain/dotnet-install.sh?

To me, it seems like this approach makes it much harder to fix issues in dotnet-install.sh because the version available at github.com is being used and local changes to dotnet-install.sh are ignored.

[livarcocc]

This has been changed already. CLI is using the dotnet-install script from the repo and we are no longer using build_tools.

[crummel]

@piotrpMSFT Do you mean CLI should stop using the BuildTools package or changing the way CLI puts it in the build_tools folder?

I think something that might be useful for all repos using bootstrap and BuildTools is something similar to the way you can use a locally built BuildTools package - you can set $BUILDTOOLS_SOURCE to a local folder and it’ll be picked up from there instead. As a long-term fix I think we should consider a $DOTNET_INSTALL_SOURCE or something similar, since I can see a scenario like: “I’m fixing a dotnet-install issue and want to test my changes in multiple repos”.