nix-beam-flakes
Nix-based BEAM toolchain management (by shanesveller)
rust-overlay
Pure and reproducible nix overlay of binary distributed rust toolchains (by oxalica)
nix-beam-flakes | rust-overlay | |
---|---|---|
1 | 11 | |
36 | 763 | |
- | - | |
9.2 | 9.5 | |
2 months ago | 5 days ago | |
Nix | Nix | |
Apache License 2.0 | MIT License |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
nix-beam-flakes
Posts with mentions or reviews of nix-beam-flakes.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-04-25.
-
Would it make sense to start a repo which contains some "standard" flake.nix files for various types of projects?
I left it vague because I didn't want to seem self-promotional. Unmerged documentation branch is the best starting place here: README, docs folder of that branch, example from develop. I daily drive it at work, and on a personal project for about 8 months. Doesn't do well for monorepos with disparate BEAM versions yet, but there are escape hatches and usage-as-library too. For the typical Phoenix project with a few extra system deps it's a pretty good onramp. perSystem.beamWorkspace.devShell.extraPackages is how you add arbitrary buildInputs like your VIPS stuff and .extraArgs for additional arguments to mkShell, such as your non-sensitive envvars. There's a page for future goals too. Publishing the rendered docs as a static site is in my TODOs, it's mostly glue left.
rust-overlay
Posts with mentions or reviews of rust-overlay.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-04-13.
-
Understanding Overlays and direnv nix shell inheritance
I'm trying to understand overlays in order to make a proper rustup install (I've read that this overlay is the best way to go).
-
Diving straight into flakes with no channels?
real-world example: https://github.com/oxalica/rust-overlay/blob/master/flake.nix
-
An example providing rust toolchain for Linux/macOS using devenv.sh
In this language context specifically, if one wanted to manage their workspace with Nix I would reach for Riff and/or oxalica/rust-overlay first, since they are deliberately more aware of Rust-specific nuance. In the latter's case it has compatibility paths with rustup-toolchain files as well, for allowing your peers who can't or won't adopt Nix to continue to feel like first-class participants in the project. Another alternative I don't have experience with would be nix-community/fenix.
-
Introducing Riff, a Nix-based tool for automatically providing external dependencies to Rust projects
p.s. I'm not sure if it's mentioned much of anywhere, but it'd be neat if there was a way to figure out the appropriate cargo from a rust-toolchain/rust-toolchain.toml if present, ala https://github.com/oxalica/rust-overlay. Funnily enough 95% of my development time is in Rust, but I don't actually have it installed globally, fun times being a NixOS user. I'd definitely make the argument that cargo is an external dependency!
-
Have a few questions about NixOS
Many of us have moved to https://github.com/oxalica/rust-overlay over Mozilla's overlay.
-
Rust Environment and Docker Build with Nix Flakes
We added rust-overlay, so we can easily specify different rust versions without relying on nixpkgs to give us what ever rust version in there.
-
Switching from pyenv, rbenv, goenv and nvm to asdf – yujinyuz
If it's Rust, you can use https://github.com/oxalica/rust-overlay to get any version you want very easily without pinning an instance of nixpkgs just for it.
asdf does not allow you to keep three different versions of the same language, so I'm not sure how that compares? It's not super-trivial to do in Nix, but at least you can do it.
asdf is also no different than Nix when it comes to minor/major versions. You're at the mercy of what the plugin does, other than that you have to create your own plugin from scratch or make a fork. Nix has the option to patch things up more easily at least.
-
Fenix: rust toolchains for all channels and rust-analyzer nightly
How does this compare to https://github.com/oxalica/rust-overlay/ ? Can fenix ingest a rust-toolchain file and provide packages from it?
Can you say a bit about how this compares to oxalica’s rust overlay?
-
What made you grok Nix language?
I frequently try to do something, say use (from the README of rust overlay):