-
Notifications
You must be signed in to change notification settings - Fork 107
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
expose flk devshell module #55
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I wonder...
What command can I run to access the shells. I've tried |
{
inputs.flake-utils.url = "github:numtide/flake-utils";
inputs.devshell.url = "github:numtide/devshell";
inputs.nixflk.uri = "github:nrdxp/nixflk";
outputs = { self, flake-utils, devshell, nixflk, nixpkgs }:
flake-utils.lib.simpleFlake {
inherit nixpkgs;
name = "my-project";
preOverlays = [ (import devshell.overlay) ];
shell = { pkgs }:
pkgs.mkDevShell {
imports = [ (import nixflk.devshellModules.flk) ];
};
};
} |
You question promoted this thought: numtide/devshell#52 (comment) |
56d6927
to
cbc7ffc
Compare
cbc7ffc
to
b083b9d
Compare
This should be (theoretically) good to go, I've rebase. Setting a precedent for sharing devshells according to discussion over at numtide/devshell#52 (comment) $ nix flake show
git+file:///home/blaggacao/ghq/github.com/nrdxp/nixflk
...
├───devshellModules: unknown
... And $ nix develop
🔨 Welcome to flk
[general commands]
hooks - install git hooks
menu - prints this menu
[linters]
nixpkgs-fmt - Nix code formatter for nixpkgs
[main]
flk - Build, deploy, and install nixflk
nix - Powerful package manager that makes package management reliable and reproducible
[servers]
grip - Preview GitHub Markdown files like Readme locally before committing them
[vcs]
git - Distributed version control system [flk]$ flk
Usage: flk [ iso | install {host} | {host} [switch|boot|test] ] |
@zimbatm would you mind giving your feedback? (mainly to make sure this attempt on devshell sharing is +- inline with your ideas or even plans, if any) |
The idea of shareable modules was for projects that want to provide extensions to the devshell. It seems that nixflk is a project template, so I would really keep things as simple as possible. If there are re-usable bits, break them out into a different project and then import them here. I haven't looked at nixflk closely so I might be wrong. |
Now, with the new devshell module system in place, the impetus of this PR merits revisiting from a different angle some time in the near future on behalf of nixflk. So I'm closing this for now and might think over it again in the coming days (hopefully, I'll find some time). * The impetus was: How can we nudge users of nixflk into sharing their (personal) devshell modules, so that other users can "follow" their favorite expert on a devshell realm (say: rust) — social stock trading style. |
a more useful attempt than #39 for #38