Add support for colon seperated list of library homes #140
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Allows setting multiple homes in a colon seperated string. e.g.
ECKIT_HOME=/path/to/home1:/path/to/home2
This is useful for libraries which like to search for multiple configs, which may be in distinct directories. LocalPathName's tilde expansion
~eckit/file
will match the first existing file from[/path/to/home1/file1, /path/to/home2/file]
. If none exist, the first is used.No change in behaviour is intended if a single home is set.
If LIB_HOME is not set, there is a change in behaviour in the tilde expansion:
~eckit/file1
->libraryprefix/file1
,libraryprefix/../file1
,libraryprefix/../../file1
,libraryprefix/../../../file1
.../file1
~eckit/file1
->libraryprefix/file1
,libraryprefix/../file1
,libraryprefix/../../file1
,libraryprefix/../../file1
,/file1
note This does mean that LIB_HOME cannot be set to directories whose path contains a colon.