Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
S
Spack
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Package registry
Container registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
eic_tools
Spack
Commits
cf76a143
Commit
cf76a143
authored
5 years ago
by
Oliver Breitwieser
Committed by
Todd Gamblin
5 years ago
Browse files
Options
Downloads
Patches
Plain Diff
libtomlc99: Update version
The PR for shared libraries has been merged upstream -> add new version.
parent
4189640e
Branches
Branches containing commit
Tags
Tags containing commit
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
var/spack/repos/builtin/packages/libtomlc99/package.py
+1
-0
1 addition, 0 deletions
var/spack/repos/builtin/packages/libtomlc99/package.py
with
1 addition
and
0 deletions
var/spack/repos/builtin/packages/libtomlc99/package.py
+
1
−
0
View file @
cf76a143
...
...
@@ -14,6 +14,7 @@ class Libtomlc99(Package):
# Since there is no official versioning, yet, just use the date and prefix
# with '0.' to make switching to proper versioning easier later.
version
(
'
0.2019.06.24
'
,
commit
=
'
b701a09579200b1bd87081d1e6a284a89b5576c8
'
)
# Unfortunately, upstream Makefile does not build shared libaries, so use
# local changes for now.
version
(
'
0.2019.05.02
'
,
commit
=
'
35118431263dec2a2a7b55e4dd717a5f54992e3e
'
,
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment