-
Notifications
You must be signed in to change notification settings - Fork 136
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
feature : add nix-kernel support #96
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.
Thanks for this! Can you:
- Rebase it on top of master, which has an updated Nixpkgs.
- Add it to the list of kernels to be tested on
tests/default.nix
. - Add a simple example, with a single command in the
examples
folder.
python3Packages.buildPythonPackage rec { | ||
pname = "nix-kernel"; | ||
version = "0.1"; | ||
src = fetchFromGitHub { | ||
owner = "GTrunSec"; | ||
repo = "nix-kernel"; | ||
rev = "dfa42d0812d508ded99f690ee1a83281d900a3ec"; | ||
sha256 = "1lf4rbbxjmq9h6g3wrdzx3v3dn1bndfmiybxiy0sjavgb6lzc8kq"; | ||
}; |
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.
Why do you use a fork of the kernel?
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.
Why do you use a fork of the kernel?
waiting for merge in. corps/nix-kernel#1
You probably merged instead of rebasing, lots of extra commits are showing in the PR. |
17997f7
to
534f07d
Compare
Based on https://github.com/corps/nix-kernel