feat(nix): add mkShell and flake
#580
Conversation
| "{pkgs ? import <nixpkgs> {}, ...}:", | ||
| "pkgs.mkShell {", | ||
| " shellHook = ''", | ||
| " $1", | ||
| " '';", | ||
| "", | ||
| " env = {", | ||
| " $2", | ||
| " };", | ||
| "", | ||
| " packages = [", | ||
| " $3", | ||
| " ];", | ||
| "}" |
There was a problem hiding this comment.
| "{pkgs ? import <nixpkgs> {}, ...}:", | |
| "pkgs.mkShell {", | |
| " shellHook = ''", | |
| " $1", | |
| " '';", | |
| "", | |
| " env = {", | |
| " $2", | |
| " };", | |
| "", | |
| " packages = [", | |
| " $3", | |
| " ];", | |
| "}" | |
| "pkgs.mkShell {", | |
| " shellHook = ''", | |
| " $1", | |
| " '';", | |
| "", | |
| " env = {", | |
| " $2", | |
| " };", | |
| "", | |
| " packages = [", | |
| " $3", | |
| " ];", | |
| "};" |
for this part I would make it both nix and flake compatible since it would be better for both compatibility and a user is expected to write pkgs.mkShell in a shell.nix file or in devShells.default
There was a problem hiding this comment.
Yeah, makes sense, but then I'd need to write the preamble manually every single time I write a shell.nix...
There was a problem hiding this comment.
Probably best to split it into two templates in that case.
| "", | ||
| " inputs = {", | ||
| " nixpkgs.url = \"github:NixOS/nixpkgs/nixos-unstable\";", | ||
| " flake-utils.url = \"github:numtide/flake-utils\";", |
There was a problem hiding this comment.
Personally I would not use flake-utils as it's not module system compliant, but I would say split up to flake-parts and flake-utils as separate snippets and do the default or just remove flake-utils from this.
There was a problem hiding this comment.
How about lib.genAttrs <SYSTEMS> (system: {}) so we'd only need nixpkgs? We could add a different flake-parts snippet but that might get out of hand quite quickly as flake.parts is quite the rabbit hole.
There was a problem hiding this comment.
I would say probably best to create one with all systems, flake utils and flake parts.
No description provided.