Conversation
Signed-off-by: Loic Pottier <[email protected]>
|
Hi @lpottier! I noticed that the following package(s) don't yet have maintainers:
Are you interested in adopting any of these package(s)? If so, simply add the following to the package class: maintainers("lpottier")If not, could you contact the developers of this package and see if they are interested? You can quickly see who has worked on a package with $ spack blame flux-pythonThank you for your help! Please don't add maintainers without their consent. You don't have to be a Spack expert or package developer in order to be a "maintainer," it just gives us a list of users willing to review PRs or debug issues relating to this package. A package can have multiple maintainers; just add a list of GitHub handles of anyone who wants to volunteer. |
|
I'm OK not being a maintainer here, but of course if you run into issues (I'm guessing this is for Mummi?) please come to me first! |
alecbcs
changed the title
tldahlgren
left a comment
tldahlgren
left a comment
There was a problem hiding this comment.
Confirmed the version sha256s and dependencies (though not an exact match for py-cffi).
3 participants
Add Flux Python API package as a standalone spack package. It's useful on system where Flux is the main scheduler (i.e., El Cap) where users want to install the Flux API but not Flux itself.
It's a python package so it should be named
py-fluxbut all Flux-related packages are namedflux-*, I followed that convention instead.@vsoch I can add you as a maintainer if you want, let me know