-
Notifications
You must be signed in to change notification settings - Fork 46
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Consider packaging and distribution on conda-forge #478
Comments
I'm not opposed in principle. Could you outline what would need to be done on my end? Note also that I've not been successful in getting Adobe licenses for some of the pFUnit stack, and some orgs don't like to play with the NOSA open source agreement. |
@tclune sure.
Feel free to tag me with questions if you'd like someone to look at if before asking for review. The conda-forge docs for the process are here: https://conda-forge.org/docs/maintainer/adding_pkgs/
NASA-1.3 is an SPDX license (https://spdx.org/licenses/NASA-1.3.html) so I think that should be fine. conda-forge allows for even non-standard modified licenses (example). |
I'm cc'ing in @pchakraborty so he can see this. We have a (simpler) package we want on conda, so we might be able to do that first for experience and then tackle pFUnit. |
@mathomp4 @pchakraborty if you'd like examples of Fortran package recipes that I've added to conda-forge here's a few: |
In addition to providing the source code and releases, it would be nice to also distribute pFUnit on conda-forge as a cross-platform distribution method, given that all of the build requirements
pFUnit/README.md
Lines 39 to 48 in 26dadb1
are already distributed on conda-forge.
This would have a beneficial impact on at least one library that I know of (c.f. Cambridge-ICCS/FTorch#264).
The text was updated successfully, but these errors were encountered: