-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
maintenance/recipe style fixes #37612
Closed
greenc-FNAL
wants to merge
199
commits into
spack:develop
from
greenc-FNAL:maintenance/recipe-style-fixes
Closed
maintenance/recipe style fixes #37612
greenc-FNAL
wants to merge
199
commits into
spack:develop
from
greenc-FNAL:maintenance/recipe-style-fixes
Conversation
This file contains 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
* New command option `spack create --limit #`. * Corresponding functionality in `spack.stage.get_checksums_for_versions()`.
Better description for fetch_more_versions() url_for_version() expects Version, not str Style fix
Initial CPAN2Spack run Handle required input during install process Add missing/corrected version info Checkpoint 1 Improve package description formatting and/or text URL updates/fixes Remove ambiguity over build system Checkpoint 2
…ured This looks to me like the best compromise regarding externals in a buildcache. I wouldn't want `spack install` on my machine to install specs that were marked external on another. At the same time there are centers that control the target systems on which spack is used, and would want to use external in buildcaches. As a solution, reuse concretization will now consider those externals used in buildcaches that match a locally configured external in packages.yaml. So for example person A installs and pushes specs with this config: ```yaml packages: ncurses: externals: - spec: ncurses@6.0.12345 +feature prefix: /usr ``` and person B concretizes and installs using that buildcache with the following config: ```yaml packages: ncurses: externals: - spec: ncurses@6 prefix: /usr ``` the spec will be reused (or rather, will be considered for reuse...)
…als-from-buildcache Port of spack#35975
…-2023-04-28 Merge from upstream including GCC 13.1.0
spackbot-app
bot
added
binary-packages
build-systems
commands
conflicts
core
PR affects Spack core functionality
defaults
dependencies
maintainers
modules
new-package
new-variant
new-version
patch
python
R
stage
tests
General test capability(ies)
update-package
utilities
virtual-dependencies
workflow
labels
May 11, 2023
PR to wrong repo. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
binary-packages
build-systems
commands
conflicts
core
PR affects Spack core functionality
defaults
dependencies
maintainers
modules
new-package
new-variant
new-version
patch
python
R
stage
tests
General test capability(ies)
update-package
utilities
virtual-dependencies
workflow
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.
scientific7
)spack style
spack style
(build|install)_time_test_callbacks
spack find
doesn't search virtual deps properly #123)