Open Ahuge opened 7 months ago
We were able to reproduce this on our end on Linux. I believe installscope is a built-in installbuilder command, so we may just need to double check its intent.
Was just double checking the main installation component, and it sets installdirprefix
based on the installation scope, which is also what's set on the GUI. If it's system, it'll use platform_install_prefix
, which according to https://releases.installbuilder.com/installbuilder/docs/installbuilder-userguide/variables.html only shows:
platform_install_prefix: The platform specific default installation path
Example values:
/home/user, C:\Program Files, /Applications
This would indicate to me that it's not just an unattended issue. Probably have to manually change that value for Linux.
Will require some testing on our end to get it right.
Thanks @epmog
I'll manually set it in the meantime!
Expected Behaviour
Perhaps this is something that I am misunderstanding, but when I install with
--installscope system
I thought that the submitter would get installed to/opt/DeadlineCloudSubmitter
, I could have sworn it used to do that? But maybe that was my imagination.I would expect a
--installscope user
to go to "$HOME/DeadlineCloudSubmitter" and a system scope to go to somewhere like "/opt/DeadlineCloudSubmitter".Current Behaviour
It appears to maybe ignore the
--installscope
setting and always go to "$HOME/DeadlineCloudSubmitter" so when I run the--installscope system
as a sudo user, it goes into "/root/DeadlineCloudSubmitter"Reproduction Steps
Install DeadlineCloudSubmitter in an unattended mode using the code snippet below
Code Snippet
./DeadlineCloudSubmitter-2024.04.17.0-linux-x64-installer.run --unattendedmodeui none --mode unattended --enable-components deadline_cloud_for_maya,deadline_cloud_for_nuke,deadline_cloud_for_houdini,blender_integrated_submitter --installscope system