Skip to content
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

Open
matthewfeickert opened this issue Jan 29, 2025 · 4 comments
Open

Consider packaging and distribution on conda-forge #478

matthewfeickert opened this issue Jan 29, 2025 · 4 comments
Assignees

Comments

@matthewfeickert
Copy link

matthewfeickert commented Jan 29, 2025

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

- Fortran compilers:
- Intel v18.0.5, v19.0.3
- NAG v6.2
- GFortran v8.3, v9.2
- CMake v3.12+
- Python v2.7* or v3.x
- make (or ninja or ...)
- Optional
- MPI (tested with OpenMPI and iMPI)
- OpenMP

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).

@mathomp4 mathomp4 self-assigned this Jan 30, 2025
@tclune
Copy link
Member

tclune commented Jan 30, 2025

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.

@matthewfeickert
Copy link
Author

matthewfeickert commented Jan 30, 2025

Could you outline what would need to be done on my end?

@tclune sure.

  1. Fork https://github.com/conda-forge/staged-recipes
  2. Make a new branch
  3. cp -r recipes/example recipes/pfunit
  4. Read through the recipes/pfunit/meta.yaml and adapt the contents of it for what is needed for pFUnit. Add and commit your changes.
  5. [Optional] Once done, run pixi run lint to lint your recipe.
  6. [Optional] Run pixi run build-<your os> to build the recipe locally to verify it passes.
  7. Open up a PR.

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/

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.

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).

@mathomp4
Copy link
Collaborator

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.

@matthewfeickert
Copy link
Author

@mathomp4 @pchakraborty if you'd like examples of Fortran package recipes that I've added to conda-forge here's a few:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants