Skip to content

Adding ability for repo paths from a manifest file to be expanded when creating an environment.#49084

Merged
becker33 merged 4 commits intospack:developfrom
fbrechin:expanding-relative-repo-paths-when-creating-envs
Mar 4, 2025
Merged

Adding ability for repo paths from a manifest file to be expanded when creating an environment.#49084
becker33 merged 4 commits intospack:developfrom
fbrechin:expanding-relative-repo-paths-when-creating-envs

Conversation

@fbrechin
Copy link
Copy Markdown
Contributor

Adding ability for repo paths from a manifest file to be expanded when creating an environment.

A unit test was added to check that an environment variable will be expanded. Also, a possible bug was fixed in the expansion of develop paths where if an environment variable was in the path that then produced an absolute path the path would not be extended.

@spackbot-app spackbot-app bot added commands core PR affects Spack core functionality environments tests General test capability(ies) labels Feb 17, 2025
@fbrechin fbrechin closed this Feb 20, 2025
fbrechin added 2 commits March 3, 2025 11:24
…n creating an environment.

A unit test was added to check that an environment variable will be expanded.
Also, a bug was fixed in the expansion of develop paths where if an environment variable
was in the path that then produced an absolute path the path would not be extended.
@fbrechin fbrechin reopened this Mar 3, 2025
…n creating an environment.

A unit test was added to check that an environment variable will be expanded.
Also, a bug was fixed in the expansion of develop paths where if an environment variable
was in the path that then produced an absolute path the path would not be extended.
@fbrechin fbrechin force-pushed the expanding-relative-repo-paths-when-creating-envs branch from c68fcc5 to 6bab18a Compare March 3, 2025 12:34
@fbrechin
Copy link
Copy Markdown
Contributor Author

fbrechin commented Mar 3, 2025

Just to note, the expansion of any relative repo paths is controlled by the existing --keep-relative option when using spack env create and is therefore on by default. The existing option previously only controlled whether to do any develop path expansion.

I would be happy to change the new repo expansion control behavior in any way, including controlling it via a separate option if preferred or setting it to always be on. I do feel that the default behavior should be for this expansion to happen though.

Feedback on this would be appreciated!

@becker33 becker33 merged commit e2293c7 into spack:develop Mar 4, 2025
37 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

commands core PR affects Spack core functionality environments tests General test capability(ies)

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants