-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
storePath as a settable property of derivation #5067
Comments
I am also reminded of how different remote builders can have different "features" to ensure that certain derivations go just to then. I think that + a union store that does a bind mount is the right way to do this. |
I marked this as stale due to inactivity. → More info |
Still wanted |
This issue has been mentioned on NixOS Discourse. There might be relevant details there: https://discourse.nixos.org/t/super-colliding-nix-stores/28462/11 |
This issue has been mentioned on NixOS Discourse. There might be relevant details there: https://discourse.nixos.org/t/install-some-nix-packages-to-other-location-than-nix-store/30770/12 |
Is your feature request related to a problem? Please describe.
I would like to store semi-large pieces of data in the Nix store. In a typical HPC environment there would be different filesystems for storing lots of small files (NFS/AFS with limited quota) and for storing large files (GPFS/Ceph with block size 256KiB or more).
Describe the solution you'd like
Would be nice to be able to define derivations that produce an output into a custom store path:
This is already partially working in a sense that an existing Nix installation can be run with different values of NIX_STORE_DIR and the same value of NIX_STATE_DIR.
Describe alternatives you've considered
The alternative is to store symlinks in the store
Lacks most of the benefits: proper garbage collection, sandboxing support, etc.
Possible overlap with #5025
The text was updated successfully, but these errors were encountered: