-
Notifications
You must be signed in to change notification settings - Fork 2
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
base: use RELEASE to determine module paths.
Right after being installed, each module adds its own path to the RELEASE file. Therefore, it is possible to use the RELEASE file as the source of truth for our dependencies' paths. Since a module cannot be built without its dependency already built, this does not limit our installation scripts. This removes duplication of several module paths, which may now be changed more easily. If a non-existent dependency is provided and errexit (-e) bash option is set, the script will fail during the get_module_path's grep call due to its non-zero exit code.
1 parent
12280c9
commit 525753f
Showing
4 changed files
with
50 additions
and
49 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters