-
Notifications
You must be signed in to change notification settings - Fork 33
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can't install on macOS with installation_path parameter #382
Comments
Hey @bdominguez and thanks for raising this. The The reason why Line 34 in 197b61b
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:
Can you document this with an example? Thanks. |
Thanks for the example @bdominguez |
One thing we could do is to properly support @bdominguez out of curiosity, what is the path of the Unity install when you select the |
Not sure what you mean. I think that if we want to fully support the 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 |
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:
The text was updated successfully, but these errors were encountered: