Here is my best attempt to articulate why I believe all dependencies, including compiler toolchains, belong in version control.

https://www.forrestthewoods.com/blog/dependencies-belong-in-version-control/

Dependencies Belong in Version Control

Why dependencies should be checked into version control.

@forrestthewoods yes! And, packaging up things like “visual studio” etc is not even that massive. IIRC at Unity I had that in like 200MB without even trying hard. This is for old version, but idea the same https://gist.github.com/aras-p/e5df1b7a3374b99ae31f053b14403d92
Packaging up Visual Studio & Windows 10 SDK for in-repository usage

Packaging up Visual Studio & Windows 10 SDK for in-repository usage - package_builds_vs2017.cmd

Gist

@aras @forrestthewoods I miss that sooooo much. Stevedore, the thing downloading all the toolchains, was one of the best part or our buildsystem at Unity!

Getting a lil bit closer now again by using https://prefix.dev/ at work to define all the tooling dependencies. But obviously it can't redistribute stuff like Visual Studio (but pins the version for that one at least :))

7 Reasons to Switch from Conda to Pixi

Pixi is conda-compatible and comes with more speed, lockfiles and tasks. It is the next-gen package manager for Python and R and more.

prefix.dev
@wumpf @aras @forrestthewoods the whole build system at unity was amazing. we were spoiled there
@logicalerror @wumpf @aras @forrestthewoods it really was the smoothest build system I've ever used for that size of projects. I still have the scoop bucket with the right version of perl to make building in a git bash shell on windows seamless.
@shana @wumpf @aras @forrestthewoods somebody should really do a public talk about the unity build system