-
Notifications
You must be signed in to change notification settings - Fork 163
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
Create Nix package #1102
Comments
somewhat relevant https://onlinelibrary.wiley.com/doi/full/10.1002/qua.26872 |
Thanks for the link, I was reading that (and https://github.com/markuskowa/NixOS-QChem) and thinking about how to get Q-Chem built this way, then realized packaging cclib is possible too. I've marked this as 2.x not because it won't get done soon, but because Nix is not the easiest thing to get working. I've made another packaging issue for Spack (#1103), but not Guix, mostly because I Don't have experience with it yet. |
It was added in Nix-QChem/NixOS-QChem#285 for version 1.7.2, but all the optional deps are missing and it looks like they're having problems with PyQt4 (Nix-QChem/NixOS-QChem#345) and that part of our code needs to be removed. This issue can be closed once a PR on their repo bumps the version to 1.8. |
I was hoping to put this in regular Nixpkgs but this is good enough. |
Note that Q-Chem versions 5.1 to 5.4 are packed with Nix (https://github.com/Nix-QChem/NixOS-QChem/tree/master/pkgs/apps/q-chem). It would also work perfectly fine to put nix files in the cclib repo itself to achieve a reproducible build and development environment. For example as we did in (pysisyphus). |
Reopening because:
|
Sorry, now I've missed your comment 😅 If you wan't I can open a PR and wrap Nix around this Repo. It can depend on NixOS-QChem and NixOS-QChem can depend on this, that's not a problem. |
If you wish, we could discuss this separately. Maybe just write me a mail to phillip.seeber@uni-jena.de. I could possibly help you out there. |
https://www.breakds.org/post/build-python-package/
The text was updated successfully, but these errors were encountered: