feat: Introduces script to generate spack's packages.yaml#6
Draft
muffgaga wants to merge 1 commit into
Draft
Conversation
* parse eessi_api_metadata_software.json * extract relevant information for spack external packages → packages.yaml * handle typical naming differences (all-lower-case in spack), variants being encoded within module name in EESSI, etc.
boegel
reviewed
May 28, 2026
| # "type": "ruby", | ||
|
|
||
| def heuristic_translate(full_module_name): | ||
| spack_package_name = full_module_name.replace("-CUDA/", "/").replace(".MPI/", "/").split("/")[0].lower() |
Collaborator
There was a problem hiding this comment.
This is a nice heuristic to start with, but I can't help wonder if there's a lightweight way to query Spack whether this is a known package name, so we can have fallback heuristics as well (like prefixing with py- for Python packages)?
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
(Yes, this is ugly… → let's discuss it; our (EBRAINS/ESD people) plan is to improve it until we can test-drive it on a EESSI install on, e.g., JUSUF/JSC with some SNN simulators (maybe arbor?).)