flake.nix: devShell: use devenv #4
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
rgoulter
force-pushed
the
use-devenv-mkshell
branch
from
15bb033 to
614fa45
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Rationale
Nix shells (
nix-shell,nix develop, which both typically make use of nixpkgs'mkShell) provide a good DX by providing tools/libraries needed to build a project. -- e.g. You get to havegradleinPATHwithout having to copy/paste installation instructions from README.Previously, I took either/or of:
mkShellin the repository that uses it; duplicating Nix code (e.g.packages = [compiler lsp linter]) in each repository.mkShellin a separate repository, referencing this from each repository.These each have advantages/disadvantages.
Using devenv is similar to (2) above; except that maintaining
[compiler lsp linter]is done in a repo which others using the tool benefit from.