Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

base: use RELEASE to determine module paths. #48

Merged
merged 2 commits into from
Feb 19, 2024
Merged

Conversation

henriquesimoes
Copy link
Collaborator

Right after being installed, a module adds its own path to the RELEASE file. Use this as the source of truth for specifying the dependencies' path in later module builds. Since a module cannot be built without its dependency already built, this does not limit our installation scripts.

This removes duplication of several paths of modules, which may now change more easily.

@henriquesimoes henriquesimoes requested a review from ericonr January 8, 2024 21:02
Copy link
Member

@ericonr ericonr left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nits:

"base: use RELEASE to determine module paths."

"..., each module adds its..."
"Therefore, it's possible to use the RELEASE file as the source of truth for our dependencies' paths"

"This removes duplication of several module paths, which may now be changed more easily."

That last phrase makes me feel like we are going to be changing a whole lot of paths :p Is that why you mentioned this being related to the final container cleanup?

@henriquesimoes
Copy link
Collaborator Author

Nits:

Thanks!

That last phrase makes me feel like we are going to be changing a whole lot of paths :p Is that why you mentioned this being related to the final container cleanup?

Yep. That's the point. Not sure if we'll really need to move things around, but it is now easier to do so if the decide this is the best option. Nevertheless, having a single point for defining such things diminishes our chances of making mistakes. ;)

@henriquesimoes henriquesimoes changed the title base: use RELEASE to determine modules path. base: use RELEASE to determine module paths. Jan 24, 2024
base/install-functions.sh Outdated Show resolved Hide resolved
Calc module conditionally adds support to Sequencer based on the
definition of SNCSEQ and not SEQ.

Fixes: 0183021 ("base: initial commit.")
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.
@henriquesimoes henriquesimoes merged commit 2864406 into main Feb 19, 2024
2 checks passed
@henriquesimoes henriquesimoes deleted the mod-path branch February 19, 2024 20:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants