microsoft
Linux support
Tested this on 2021.3.12f1 and 2021.3.13f1.
It seems that Unity components for Linux are just archives of two types - some are .tar.xz and some are .pkg same as for Mac. The actual components list and paths to components are listed in configuration file, for example see https://download.unity3d.com/download_unity/8af3c3e441b1/unity-2021.3.12f1-linux.ini
Also they provide a small executable that can be used to install components, e.g. https://download.unity3d.com/download_unity/8af3c3e441b1/UnitySetup-2021.3.12f1
So to make Install-UnitySetupPackage work, I made a preliminary donwload of these config and installer. Also I added PsIni module as a dependency to read config in a more or less common way, but it seems that CI check doesn't like it for some reason.
Found a related issue https://github.com/microsoft/unitysetup.powershell/issues/41
PS modules need to be installed explicitly in the build steps. You can add the install of PSIni next to the powershell-yaml one here.
It took a while to find some spare time, but now all mentioned issues should be fixed
@jwittner I re-requested review and leave conversations resolve to you
Also I made a couple of side fixes, for example I discovered that ProjectSettings.asset in project I work on contain non-valid YAML entries with empty keys and therefore throw an error on Start-UnityEditor. I can't find related issues from other users though, but I remember I saw them and believe this is not just our team issue
https://github.com/microsoft/unitysetup.powershell/pull/241/files#diff-aa0aa9d7efd11637a00cae86e7c08b97cd225609a42293d59bdf2d35059dbb47R145
Thanks for the updates. Will try to get to this ASAP next week, have a great weekend!
Getting close now! Once we resolve these last issues I'll pull down the branch and run some tests too.
Finally pushed update with -Resolve removal :sweat: I feel sorry for such long delay