spack - A flexible package manager that supports multiple versions, configurations, platforms, and compilers.

Age	Commit message (Collapse)	Author	Files	Lines
2024-01-02	Update copyright year to 2024 (#41919)	Todd Gamblin	1	-1/+1
	It was time to run `spack license update-copyright-year` again.
2023-04-19	make version(...) kwargs explicit (#36998)	Harmen Stoppels	1	-1/+1
	- [x] Replace `version(ver, checksum=None, *kwargs)` signature with `version(ver, checksum=None, , sha256=..., ...)` explicitly listing all arguments. - [x] Fix various issues in packages: - `tags` instead of `tag` - `default` instead of `preferred` - `sha26` instead of `sha256` - etc Also, use `sha256=...` consistently. Note: setting `sha256` currently doesn't validate the checksum length, so you could do `sha256="a"*32` and it would get checked as `md5`... but that's something for another PR.
2023-01-18	license year bump (#34921)	Harmen Stoppels	1	-1/+1
	* license bump year * fix black issues of modified files * mypy * fix 2021 -> 2023
2022-08-04	Git Ref versions can be paired to defined versions in the spec (#30998)	psakievich	1	-0/+17
	The current use of git ref's as a version requires a search algorithm to pick the right matching version based on the tags in the git history of the package. This is less than ideal for the use case where users already know the specific version they want the git ref to be associated with. This PR makes a new version syntax [package]@[ref]=[version] to allow the users to specify the exact hash they wish to use.