Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

build(nix): move to unstable channel #994

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

Closed

Conversation

Copy link
Contributor

@RaitoBezarius RaitoBezarius commented Nov 6, 2023
edited
Loading

As NixOS 23.11 will be out soon and the shell.nix is broken due to MSRV requirements (23.05 has 1.69.0, not 1.70.0), we can already move to unstable which is "beta 23.11" at this point.

Checklist

  • Sensible git history (for example, squash "typo" or "fix" commits). See the Rewriting History guide for help.
  • Update the changelog (if necessary)

As NixOS 23.11 will be out soon and the `shell.nix` is broken
due to MSRV requirements (23.05 has 1.69.0, not 1.70.0), we
can already move to unstable which is "beta 23.11" at this point.
Copy link
Member

phip1611 commented Nov 7, 2023
edited
Loading

https://github.com/rust-osdev/uefi-rs/blob/main/shell.nix#L20

Hm, our nix shell comes with rustup. We don't use rustc from nixpkgs. What do you mean by it's not working then? rustup installs the proper toolchain.

Copy link
Contributor Author

RaitoBezarius commented Nov 7, 2023 via email

NIX_PATH was rewired to the nixpkgs you provide inside that shell, therefore anyone who is not using rustup like me but rustc or cargo will only have errors on even basic checking. Le mar. 7 nov. 2023, 08:12, Philipp Schuster ***@***.***> a écrit :
...
https://github.com/rust-osdev/uefi-rs/blob/main/shell.nix#L20 Hm, our nix shell comes with rustup. We don't use rustc from nixpkgs. What do you mean by it's not working? — Reply to this email directly, view it on GitHub <#994 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AACMZRGT53LYJIQP54HUQMLYDHNMFAVCNFSM6AAAAAA7ABHFQOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTOOJXHEZTGNJWG4> . You are receiving this because you authored the thread.Message ID: ***@***.***>

Copy link
Member

phip1611 commented Nov 7, 2023
edited
Loading

I see. Personally, even on Nix, I'm a big rustup fan and don't like the "pure Nix"-way when it comes to Rust in a shell. But I see that some folks don't want to use rustup.

Instead of switching to nixpkgs-unstable, I think, a better solution would be to either
a) use rust-overlay and add the latest stable rust toolchain into the PATH
b) switch to a flake-based shell and provide one rustup shell and one with a pinned rustc.

What do you say?

@phip1611 phip1611 self-assigned this Nov 7, 2023
Copy link
Contributor Author

I see. Personally, even on Nix, I'm a big rustup fan and don't like the "pure Nix"-way when it comes to Rust in a shell. But I see that some folks don't want to use rustup.

Instead of switching to nixpkgs-unstable, I think, a better solution would be to either a) use rust-overlay and add the latest stable rust toolchain into the PATH b) switch to a flake-based shell and provide one rustup shell and one with a pinned rustc.

I think a) or c) is fine where c) could be just the same setup with 2 shells attribute sets instead of a Flake as I don't think it's necessary at all.

Copy link
Member

Superseded by #1007

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

AltStyle によって変換されたページ (->オリジナル) /