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

Packaging of dfnWorks with nix #80

Open
nialov opened this issue Apr 11, 2024 · 0 comments
Open

Packaging of dfnWorks with nix #80

nialov opened this issue Apr 11, 2024 · 0 comments

Comments

@nialov
Copy link

nialov commented Apr 11, 2024

Hey,

This is mostly just a FYI but I have gone through the effort of packaging dfnWorks for the nix package manager (https://nixos.org/). See here for the build definitions: https://github.com/nialov/nix-extra/blob/master/overlays/packages/dfnworks/default.nix and https://github.com/nialov/nix-extra/blob/master/overlays/packages/dfnworks/pydfnworks.nix

nix provides reproducible (and cached builds) of any software. This means it is possible to always reproduce a build with nix if you for instance provide a revision of the repo with the nix build declarations. E.g.

nix build github:nialov/nix-extra/d905dc7eca43321db38ee985ea8f10ae56de9b7c#dfnworks

Anyway, if you have had trouble with e.g. reproducibility and with developers setting up their development environment, nix is a solution to these problems although it has a steep learning curve. I have not included my packaging efforts in nixpkgs (https://github.com/NixOS/nixpkgs), as I do not know dfnWorks well enough to say if the produced build result, even with examples passing (python3 driver.py for e.g. mapdfn and faults), is completely valid. Let me know if any you actual maintainers have interest in these things! Otherwise, as said at the start, this is just a FYI.

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

1 participant