You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 27, 2024. It is now read-only.
In the POST INSTALL section, the cp commands should probably have the source directories fully qualified (can be obtained at startup of the script). Doing this script manually as I did have the risk of not being in the right place (working directory). Similarly, if someone changes the script elsewhere in the future. I guess you know that 'ressources' is misspelled, but that may be hard to change.
The text was updated successfully, but these errors were encountered:
No problems if no changes in directory structure after git clone ....
I installed from /tmp, from /root - no issues.
Script "knows" the path to the ressourses or any other directory, because these path is RELATIVE from "script root" - where script was started.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
In the POST INSTALL section, the cp commands should probably have the source directories fully qualified (can be obtained at startup of the script). Doing this script manually as I did have the risk of not being in the right place (working directory). Similarly, if someone changes the script elsewhere in the future. I guess you know that 'ressources' is misspelled, but that may be hard to change.
The text was updated successfully, but these errors were encountered: