nix: make usage in non-flake setups easier #296
+45
−22
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
using the nix expressions in setups where flakes aren't in use was possible, but a little unwieldy (you had to reconstruct the overlay defined in the flake to get copyparty in your nixpkgs set). this pr moves the overlay into it's own dedicated file, allowing it to be used directly without requiring something like flake-compat. there's also some extra documentation, illustrating how to use the module in a non-flake nixos setup.
i've also added a commit that removes a (seemingly) unnecessary evaluation of nixpkgs, to avoid contributing to the "1000 instances of nixpkgs" issue. this one might be a little controversial, so i've added it as a suggestion - if you're not interested in this change, i'll happily drop the commit. it's not super necessary for anything, just a potential optimisation i spotted.
this pr complies with the dco; https://developercertificate.org/