Conversation
|
@microsoft-github-policy-service agree |
9115ed0 to
eecc44f
Compare
|
@microsoft-github-policy-service agree |
|
Found a related issue |
jwittner
left a comment
There was a problem hiding this comment.
Thanks for the awesome contribution! Left some feedback. =)
|
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 |
|
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 |
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.xzand some are.pkgsame 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.iniAlso 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-UnitySetupPackagework, I made a preliminary donwload of these config and installer. Also I addedPsInimodule 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.