Currently, paths.sh will set the value of path variables within the OpenUxAS repository unconditionally. So the user has no opportunity to override the definition of any of those paths. This doesn't seem right. A user-provided value for these variables should be used, to allow greater control over the build automation and other scripts. Possibly, a warning could be issued when a path value is already given by the user.
Currently,
paths.shwill set the value of path variables within the OpenUxAS repository unconditionally. So the user has no opportunity to override the definition of any of those paths. This doesn't seem right. A user-provided value for these variables should be used, to allow greater control over the build automation and other scripts. Possibly, a warning could be issued when a path value is already given by the user.