Replies: 5 comments
|
As much as I'd be thrilled to remove Perl code from the library, it's used to build from non-release branches. |
0 replies
|
Yeah, Perl makes daily performance testing of the latest code commit using Spack on Mac impossible. |
0 replies
|
Perl ships with MacOS - why do you need to install it from Spack? |
0 replies
|
Instead of running the Perl scripts at configure time, we could set up a CI action that runs them and errors if there were changes. Then you'd only need Perl if you modified a public API call, updated the error categories, etc. |
0 replies
|
We now check in the Perl-generated files, so Perl is no longer necessary to build the library (as long as you don't change the input files). |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Spack installation of Perl on Mac is problematic:
https://github.com/hyoklee/hdf5/runs/6042719583?check_suite_focus=true
less dependency = more portability
All reactions