fix(nix): resolve issues and revamp the flake #184
Merged
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.
Community Contribution License Agreement
By creating this pull request, I grant the project maintainers an unlimited,
perpetual license to use, modify, and redistribute these contributions under any terms they
choose, including both the AGPLv3 and the Fossorial Commercial license terms. I
represent that I have the right to grant this license for all contributed content.
Description
This fixes up some inconsistencies and regressions with the Nix flake in this repository.
nixpkgswas 1.24, while the current required toolchain version is 1.25.nixpkgsfunction that automatically filters ALL files found in.gitignoretransparently.Additionally, I decided to follow Nix best practices and avoid antipatterns such as
with, as described in https://nix.dev/guides/best-practices; instead,inheritis used whenever possible.I also took the liberty of adding myself as a maintainer for the Nix package, and will likely do so in
nixpkgsas well for future updates, since over there the Nix version is still stuck on 1.5.2, rather than the latest 1.6.0, again at time of writing.How to test?
Build the Nix package using
nix build, and also drop into the Nix devshell usingnix developto make sure the correct version of Go and all other Go SDK tooling is still available.