-
Notifications
You must be signed in to change notification settings - Fork 15
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
fix(installer): fix installer system installs #203
fix(installer): fix installer system installs #203
Conversation
c364f4e
to
9691013
Compare
9691013
to
8c159a0
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks Lucas! Just one quick question.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry one more question
Signed-off-by: Lucas Eckhardt <117225985+lucaseck@users.noreply.github.com>
eb3dae7
to
9fd205c
Compare
Quality Gate passedIssues Measures |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
looks good!
Fixes: #197
What was the problem/requirement? (What/Why)
The installer was not installing deadline cloud for Houdini correctly when doing a system wide install. The package file was only ever being placed in the default Houdini user pref directory.
What was the solution? (How)
Swapped the installer component to use the env var
HOUDINI_PACKAGE_DIR
so that both user and system installs work. A nice additional benefit is that we don't have to have multiple subcomponents to select for each version of Houdini anymore.What is the impact of this change?
Future installers will work to install Deadline Cloud for Houdini with both user and system installations.
How was this change tested?
Manually built both Windows and Linux installers and:
On just Windows I verified that I could install over an existing installation with the current method of putting the package file in the default user pref directory. The previous installation package file was deleted from the default user pref directory. The new installation then set HOUDINI_PACKAGE_DIR. Verified in Houdini's Asset Manager that the correct path to the Node definition was being picked up.
Yes
Was this change documented?
No
Is this a breaking change?
No
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.