Closed hfossli-agens closed 2 years ago
The way the Unity installer works (worked?) is that it moves the version of Unity you want to modify into "/Applications/Unity" before it applies changes to it. u3d moves the version it works on into this location, and delegates the installation of the pkg modules to installer
which requires sudo
(see here).
From the man page
The installer command requires root privileges to run. If a package requires authentication (set in a package's .info file) the installer must be either run as root or with the sudo(8)
command (but see further discussion under the -store option).
Newer versions of Unity may not have this requirement, but as far as I know they work the same.
You can pass the password for sudo into your environment and that's how we use u3d to install things. Does that help?
I see. Thanks for enlightening me. We will use the password approach.
Why is it necessary to install with password/sudo?
On our build system we need to support multiple versions of unity and our approach is to have look at xcode, unity, rubygems etc etc as dependencies the build script can install on demand. Sudo commands is therefore not a perfect match.
We can of course find workarounds, but ideally we could install unity locally without sudo. Is it possible?