Skip to content

Move %compiler last in static spec strings#49438

Merged
alalazo merged 2 commits intodevelopfrom
hs/fix/move-compiler-in-spec-str
Mar 12, 2025
Merged

Move %compiler last in static spec strings#49438
alalazo merged 2 commits intodevelopfrom
hs/fix/move-compiler-in-spec-str

Conversation

@haampie
Copy link
Copy Markdown
Member

@haampie haampie commented Mar 12, 2025

Context: #44379

This moves %compiler and %compiler@... after variants, arch, versions in all static spec strings in the Spack codebase.

The reason for this is that % will change meaning in Spack v1.0 from "compiler attribute" to "direct dependency". Currently in a spec string pkg %gcc +feature the +feature variant refers to pkg, in the future it will refer to gcc. It mirrors what we're used to from pkg ^dep +feature.

This PR was generated by parsing all string constants as specs from

  1. the abstract syntax tree of all *.py files
  2. the json and yaml trees of all *.yml, *.yaml, *.json files

Dynamically created spec strings are not caught.

@spackbot-app

This comment was marked as off-topic.

@spackbot-app

This comment was marked as off-topic.

@spackbot-app spackbot-app bot added conflicts core PR affects Spack core functionality dependencies intel patch python tests General test capability(ies) update-package labels Mar 12, 2025
@spackbot-app spackbot-app bot added the gitlab Issues related to gitlab integration label Mar 12, 2025
Copy link
Copy Markdown
Member

@adamjstewart adamjstewart left a comment

Choose a reason for hiding this comment

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

py-* and xgboost changes look good to me. I'm not really affected by backwards-incompatible changes, but I'm sure someone would find the proposed changes to % controversial.

@elliottslaughter
Copy link
Copy Markdown
Contributor

legion looks ok. No opinion on the rest of this change.

@alalazo alalazo self-assigned this Mar 12, 2025
@alalazo
Copy link
Copy Markdown
Member

alalazo commented Mar 12, 2025

Gitlab failures are all unrelated. For reference the pipelines are: https://gitlab.spack.io/spack/spack/-/pipelines/1010868

I'm force merging, since pipelines are ❌ on develop for the same reasons they are in this PR.

@alalazo alalazo merged commit f89a2ad into develop Mar 12, 2025
34 of 35 checks passed
@alalazo alalazo deleted the hs/fix/move-compiler-in-spec-str branch March 12, 2025 18:41
@tgamblin tgamblin added this to the v1.0.0 milestone Mar 13, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

conflicts core PR affects Spack core functionality dependencies gitlab Issues related to gitlab integration intel patch python tests General test capability(ies) update-package

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants