diff options
| author | Peter Scheibel <scheibel1@llnl.gov> | 2023-10-17 11:33:59 -0700 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2023-10-17 20:33:59 +0200 |
| commit | 9cde25b39e8ca20e262dca2d8f145770db284b73 (patch) | |
| tree | 99940017575e5ec94cad82965704ce96b083013f /CITATION.cff | |
| parent | 49ea0a8e2ece302528ecd2b141298eb27114fb1e (diff) | |
| download | spack-9cde25b39e8ca20e262dca2d8f145770db284b73.tar.gz spack-9cde25b39e8ca20e262dca2d8f145770db284b73.tar.bz2 spack-9cde25b39e8ca20e262dca2d8f145770db284b73.tar.xz spack-9cde25b39e8ca20e262dca2d8f145770db284b73.zip | |
Allow / in GitVersion (#39398)
This commit allows version specifiers to refer to git branches that contain
forward slashes. For example, the following is valid syntax now:
pkg@git.releases/1.0
It also adds a new method `Spec.format_path(fmt)` which is like `Spec.format`,
but also maps unsafe characters to `_` after interpolation. The difference is
as follows:
>>> Spec("pkg@git.releases/1.0").format("{name}/{version}")
'pkg/git.releases/1.0'
>>> Spec("pkg@git.releases/1.0").format_path("{name}/{version}")
'pkg/git.releases_1.0'
The `format_path` method is used in all projections. Notice that this method
also maps `=` to `_`
>>> Spec("pkg@git.main=1.0").format_path("{name}/{version}")
'pkg/git.main_1.0'
which should avoid syntax issues when `Spec.prefix` is literally copied into a
Makefile as sometimes happens in AutotoolsPackage or MakefilePackage
Diffstat (limited to 'CITATION.cff')
0 files changed, 0 insertions, 0 deletions