Fix #790, allow directories and symlinks in FILELIST. #1158
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.
Describe the contribution
Checks a name-based subdirectory under ${MISSION_DEFS} for files listed in the FILELIST for that target. If file is a symlink, the link should be followed so the correct content is installed, not a symlink.
Fixes #790
Testing performed
Created a symlink in a target name subdirectory (see additional context) and confirm that the correct file content is installed.
Expected behavior changes
Items in FILELIST can be in a target name directory, and may be symlinks.
System(s) tested on
Ubuntu 20.04
Additional context
This also adds another "NOTE" message to indicate exactly what file is being used, after all lookup/de-mapping logic is done, e.g. I made a symlink to test this out:
This is similar to all the other informational messages for table sources and app sources indicating where they were found.
Contributor Info - All information REQUIRED for consideration of pull request
Joseph Hickey, Vantage Systems, Inc.