fenix
nixpkgs
Our great sponsors
| fenix | nixpkgs | |
|---|---|---|
| 19 | 975 | |
| 560 | 15,656 | |
| 7.1% | 5.3% | |
| 9.5 | 10.0 | |
| 7 days ago | 4 days ago | |
| Nix | Nix | |
| Mozilla Public License 2.0 | MIT License |
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.
fenix
-
Use nix-shell or systemPackages
Rustup works as is. Though note that Nix supplants all such toolchain installers such as Rustup, nvm, etc. I.e. instead of Rustup there is fenix.
-
Can rustc generate identical binaries, with the same hash, from the same souce code?
Fenix ( https://github.com/nix-community/fenix ) has tooling or picking a specific toolchain or even nightly. You can then build with the following nix code:
- Fenix: Rust toolchains and rust-analyzer nightly for Nix
-
Annoucing fenix monthly, Rust toolchains updated 1st of every month
Fenix monthly is a new branch similar to the main branch, but only updated on the 1st of every month, for cases where you want to use rust nightly but don't need it to be updated very often.
- Fenix - Rust toolchains and rust-analyzer nightly for Nix
- Show HN: Fenix – Rust toolchains and Rust-analyzer nightly for Nix
-
Why this overlay doesn't work?
The issue should be fixed once the nix-vscode-extension and fenix patches are merged. The latter will happen automatically once CI passes.
-
Have a few questions about NixOS
4. I would suggest Mozilla's Rust overlay or fenix or similar instead of Rustup - that would be more of the "Nix-way" to acquire the toolchain and you can still manage multiple versions. Not sure what the Ruby equivalent is, I don't do Ruby.
-
Oops, I Did It Again...I Made A Rust Web API And It Was Not That Difficult
To follow along, you'll need a stable Rust toolchain. See the install page for instructions to install rustup for your platform. You should prefer this method to your distribution's package manager. If you're a NixOS freak, I recommend fenix.
- Fenix: rust toolchains for all channels and rust-analyzer nightly
nixpkgs
- Maintainers Leaving
-
Air Force picks Anduril, General Atomics to develop unmanned fighter jets
https://github.com/NixOS/nixpkgs/commits?author=neon-sunset
-
Eelco Dolstra's leadership is corrosive to the Nix project
I see two signers in the top 6 displayed on https://github.com/NixOS/nixpkgs/graphs/contributors
-
3rd Edition of Programming: Principles and Practice Using C++ by Stroustrup
For a single file script, nix can make the package management quite easy: https://github.com/NixOS/nixpkgs/blob/master/doc/languages-f...
For example,
```
- NixOS/nixpkgs: There isn't a clear canonical way to refer to a specific package
-
NixOS Is Not Reproducible
Yes, Nix doesn't actually ensure that the builds are deterministic. In fact it works just fine if they aren't. There are packages in nixpkgs that aren't reproducible: https://github.com/NixOS/nixpkgs/issues?q=is%3Aopen+is%3Aiss...
-
The xz attack shell script
I'm not familiar with Bazel, but Nix in it's current form wouldn't have solved this attack. First of all, the standard mkDerivation function calls the same configure; make; make install process that made this attack possible. Nixpkgs regularly pulls in external resources (fetchUrl and friends) that are equally vulnerable to a poisoned release tarball. Checkout the comment on the current xz entry in nixpkgs https://github.com/NixOS/nixpkgs/blob/master/pkgs/tools/comp...
-
Debian Git Monorepo
NixOS uses a monorepo and I think everyone's love it.
I love being able to easily grep through all the packages source code and there's regularly PRs that harmonizes conventions across many packages.
Nixpkgs doesn't include the packaged software source code, so it's a lot more practical than what Debian is doing.
https://github.com/NixOS/nixpkgs
-
From xz to ibus: more questionable tarballs
In this specific case, nix uses fetchFromGitHub to download the source archive, which are generated by GitHub for the specified revision[1]. Arch seems to just download the tarball from the releases page[2].
[1]: https://github.com/NixOS/nixpkgs/blob/3c2fdd0a4e6396fc310a6e...
[2]: https://gitlab.archlinux.org/archlinux/packaging/packages/ib...
-
GitHub Disabled the Xz Repo
True, but irrelevant -- _some packages_, _somewhere_, do depend on xz, which, if built, requires pulling the source from GitHub (see the default.nix: https://github.com/NixOS/nixpkgs/blob/nixos-23.11/pkgs/tools...)
It's not the vulnerability that's a problem right now (NixOS was protected by a couple of factors) but rather GitHub's hamfisted response.
That is the problem.
What are some alternatives?
rust-overlay - Pure and reproducible nix overlay of binary distributed rust toolchains
asdf - Extendable version manager with support for Ruby, Node.js, Elixir, Erlang & more
nixos-flake-example - This is a demo NixOS config, with optional flakes support. Along with notes on why flakes is useful and worth adopting.
Home Manager using Nix - Manage a user environment using Nix [maintainer=@rycee]
Nightlies - Nightly builds for DuckieTV
git-lfs - Git extension for versioning large files
anyhow - Flexible concrete Error type built on std::error::Error
easyeffects - Limiter, compressor, convolver, equalizer and auto volume and many other plugins for PipeWire applications
nix-cargo-integration - Library to easily and effortlessly integrate Cargo projects with Nix.
spack - A flexible package manager that supports multiple versions, configurations, platforms, and compilers.
lazy-static.rs - A small macro for defining lazy evaluated static variables in Rust.
waydroid - Waydroid uses a container-based approach to boot a full Android system on a regular GNU/Linux system like Ubuntu.