-
-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
Refactor Nix flake to use crane #7763
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 can't really review this since I don't use nix anymore but from what I remember from my days this seems reasonable 👍 Thanks!
e86b983
to
34398d4
Compare
34398d4
to
834b7b6
Compare
This resolves a build issue with nci/dream2nix and git dependencies. We can keep most of the helix-specific parts of the flake, we just need to switch from configuring nci to calling craneLib functions. We also switch to flake-utils from flake-parts: * Using rust-overlay with flake-parts directly is unergonomic (see hercules-ci/flake-parts#83). * Removing flake-parts reduces the overall dependencies: rust-overlay already depends on flake-utils.
834b7b6
to
2c1e1bf
Compare
nci = { | ||
url = "github:yusdacra/nix-cargo-integration"; | ||
inputs.nixpkgs.follows = "nixpkgs"; | ||
crane = { |
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.
We could also remove crane and use only rust-overlay like nil does. Crane has some nice helpers for the checks
and it seems to be very popular and stable though so I think it's fine to depend on it for now. If it becomes a problem in the future though, pure rust-overlay
is an option
This resolves a build issue with nci/dream2nix and git dependencies. We can keep most of the helix-specific parts of the flake, we just need to switch from configuring nci to calling craneLib functions. We also switch to flake-utils from flake-parts: * Using rust-overlay with flake-parts directly is unergonomic (see hercules-ci/flake-parts#83). * Removing flake-parts reduces the overall dependencies: rust-overlay already depends on flake-utils.
This resolves a build issue with nci/dream2nix and git dependencies. We can keep most of the helix-specific parts of the flake, we just need to switch from configuring nci to calling craneLib functions. We also switch to flake-utils from flake-parts: * Using rust-overlay with flake-parts directly is unergonomic (see hercules-ci/flake-parts#83). * Removing flake-parts reduces the overall dependencies: rust-overlay already depends on flake-utils.
This resolves a build issue with nci/dream2nix and git dependencies. We can keep most of the helix-specific parts of the flake, we just need to switch from configuring nci to calling craneLib functions.
We also switch to flake-utils from flake-parts:
Closes #7761