Open bdominguez opened 4 years ago
Hey @bdominguez and thanks for raising this.
The installation_path
on Mac does not seem to work with paths per say, as the Unity package installer expects a volume to be passed as an argument.
The reason why installation_path
does not work when you try to replicate the vanilla behaviour is because the default path isn't /Applications/Unity_2019.2.12f1, but rather
https://github.com/DragonBox/u3d/blob/197b61bc514e5322905b1efb5fff5319150ca920/lib/u3d/installer.rb#L34
You would need to run u3d install 2019.2.12f1 --installation_path / --verbose
to replicate the default behaviour.
This is definitely an issue, and if this is an option we are not able to provide due to limitation with the Unity package installer, we should not offer it in the first place.
Note that this is an option that we offered for a very long time, so maybe something changed in the Unity package installer. WDYT @lacostej ?
I have solved it indicating the volume where we have the SSD. Example:
u3d install 2019.2.12f1 -p Unity,WebGL --installation_path '/Volumes/Macintosh HD'
Can you document this with an example? Thanks.
Thanks for the example @bdominguez
One thing we could do is to properly support installation_path
as it is meant from the user mind and convert it to the volume where appropriate. From a user perspective it would be consistent. @niezbop WDYT?
@bdominguez out of curiosity, what is the path of the Unity install when you select the /Volumes/Macintosh HD
volume?
convert it to the volume where appropriate
Not sure what you mean. I think that if we want to fully support the installation_path
option for Mac, we shouldn't support the Unity package argument, but rather implement some kind of temporary moving to /Applications as we do with modules, so that we can put Unity anywhere we want on the system.
However, this would require further investigation in my mind since it means that we bypass Unity's location restriction, which we should understand before anything. I'm not sure why they set this restriction, but I'd rather not add a feature that introduces more issues than it solves!
The Hub is actually installing the packages under /Applications/Unity/Hub/Editor/<version>
so it's not a default location.
I bet they are just moving around and renaming editor packages at will.
I don't know if it's an error or if I don't use it correctly but it seems that if I add "installation_path" parameter, it doesn't work.
In theory doing that I'm simulating the same as not passing the parameter, right? Because by default it installs it in that directory. Why doesn't it work for me?
Command:
Full verbose log: