Unity package is extremely problematic

[foxscore]

Describe issue

The Unity package UnityTechnologies.Unity is not suitable for a package manager, as it will always try to install the latest version.
This leads to the newest version (which won't even be used) to be installed and just waste (at minimum) 10GB.

Managing Unity installations is UnityHub's job, since the Unity version you are using differs from project to project.

Solution

Remove the Unity package and don't allow for it to be commited again.

[jedieaston]

Once there is a way of freezing version numbers this won’t be a problem anymore. Unity Hub is in the repo, if you want to use it you can.

[foxscore]

Once there is a way of freezing version numbers this won’t be a problem anymore. Unity Hub is in the repo, if you want to use it you can.

I am aware of Unity hub being in the repo, but freezing version numbers doesn't help.
The only solutions would be to either add "Channels" (like snap), or to add every mayor Unity version seperatly
EDIT: Seperate channels wouldn't help, since you'd only be able to have one Unity version at a time

[denelon]

@foxscore it sounds like you're describing the way Java JDKs and a few other tools are added. The "major" versions are treated like separate packages. The pin feature microsoft/winget-cli#476 would just prevent the Windows Package Manager from updating a package with winget upgrade --all.

[jedieaston]

I understand now. I can work on moving these at some point (if someone gets to it before me, by all means....)

[SiJiL82]

Can the Unity package just get pulled? There needs to be moderation of packages, instead of just letting people add ones that then stick around causing issues.
It's not like the package is being kept up to date - it's currently telling me to upgrade 2019.4.31f1 to 2020.3.19f1, even though 2020.3.21f1 is the latest 2020 version, not 19f1

[jedieaston]

They were split up by major version number already, I think part of the problem is that we don't have the 2019 installers in there (which is why it's telling you to upgrade to 2020.x).

I don't really want to pull them because I feel like pinning will resolve it. Maybe it won't, but if it won't we need to revisit how the heck we're going to deal with versioned SDKs because pretty much all of the programming language manifests have been added presuming that we'll be able to pin to allow people to stick to specific versions without making a ton of IDs.

[denelon]

We're working on:

• Pin a package winget-cli#476