Skip to content

docs/Conflicts and requirements: elaborate on specs and provide link for more when arg examples#48773

Closed
tldahlgren wants to merge 3 commits intospack:developfrom
tldahlgren:docs_conflicts_when
Closed

docs/Conflicts and requirements: elaborate on specs and provide link for more when arg examples#48773
tldahlgren wants to merge 3 commits intospack:developfrom
tldahlgren:docs_conflicts_when

Conversation

@tldahlgren
Copy link
Copy Markdown
Contributor

@tldahlgren tldahlgren commented Jan 29, 2025

Questions about what specs are supported in conflicts args keep coming up so expand the main section in the docs to elaborate on args and provide a link to the "common" when= cases.

Post-1e018c3 version can be seen at https://spack--48773.org.readthedocs.build/en/48773/packaging_guide.html#conflicts-and-requirements.

@spackbot-app spackbot-app bot added core PR affects Spack core functionality documentation Improvements or additions to documentation labels Jan 29, 2025
@tldahlgren tldahlgren requested a review from scheibelp January 30, 2025 17:44
@scheibelp scheibelp self-assigned this Jan 30, 2025
Copy link
Copy Markdown
Member

@scheibelp scheibelp left a comment

Choose a reason for hiding this comment

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

There's one issue where I think we are linking to the wrong section, and I have a suggestion.

@@ -2789,13 +2798,15 @@ Adding the following to a package:
"please use a newer release."
)
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

(suggestion) I would recommend emphasizing that conflicts can be an arbitrary spec with compiler/version/architecture/dependency portions, and fleshing out this example to demonstrate.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

I expanded on part of this above and added another couple of examples below that are similar to some I've encountered reviewing PRs (nearly a month ago). Do you want more changes here?

@tldahlgren
Copy link
Copy Markdown
Contributor Author

Closing in favor of #51033 since the packaging guide has been split into multiple files.

@tldahlgren tldahlgren closed this Jul 22, 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 documentation Improvements or additions to documentation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants