flake-utils
nixpkgs
Our great sponsors
flake-utils | nixpkgs | |
---|---|---|
8 | 975 | |
1,012 | 15,656 | |
6.5% | 5.3% | |
5.8 | 10.0 | |
about 2 months ago | 4 days ago | |
Nix | Nix | |
MIT License | 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.
flake-utils
- Nix Flakes
-
Our Roadmap for Nix
The ‘flake-utils’ readme is a pretty good jumping off point: https://github.com/numtide/flake-utils
I have this or that nitpick with FL and FLP but overall it’s very solid stuff. FLP is a little more “magical”, and that’s not always the best starting out, but you really can’t go wrong with either.
-
Rust Environment and Docker Build with Nix Flakes
We added two inputs, the first is nixpkgs which lets us specify which version of nixpkgs we should use. There are many thousands of packages in the nixpkg repository, and they are updated often so here will use the unstable branch. We also added flake-utils which helps us generalize the flake to support multiple systems, not just Linux.
-
Getting Started Using Nix Flakes As An Elixir Development Environment
The inputs is how you can import external sources of other flakes into the flake project you have. In other words, any project you may need or tools required to get started, this is where you will define their source. Example below is using the standard nixpkgs and a tool called flake-utils, which provides a set of functions to make flake nix packages simpler to set up without external dependencies.
-
Flake equivalent to `nix-shell --pure`?
I'm not sure what nix-shell --pure does, but is it equivalent to using a flakes.nix in your projects? Ie i use https://github.com/numtide/flake-utils and direnv to replicate the old shell.nix with a Flakes setup. Per project i have a flakes.nix and a flakes.lock, so it feels just like my old shell.nix setup, but using flakes instead.
-
Workspace Management With Nix Flakes: Jupyter Notebook Example
A Nix Flake is just an object - check out those surrounding curly braces. This object has two keys, inputs and outputs. The inputs are where we define the flake's dependencies and where to find all the tools we use. This one has two, nixpkgs and flake-utils. Each of these just points to a GitHub URL, and if you follow those links, you'll see each repo provides its own flake.nix. The outputs of each remote flake get piped into the inputs of my flake, so we can use what they provide.
-
How to transition from shell.nix to flake.nix?
You can easily transition your shell.nix (and default.nix) to a flake-based one by using flake-utils and flake-compat. The former is actually unnecessary, but I would recommend it for typical project environments. Unless you have an impure dependency, this transition would be easy.
-
Is there a way to use flakes to nix run emacsgcc?
Flakes can provide different types of things: - some flakes provide applications that you can nix run, - some flakes provide functions that you can import (e.g. https://github.com/numtide/flake-utils), - some flakes provide overlays to use with nixpkgs (e.g. that emacs-overlay you posted).
nixpkgs
-
Nix: The Breaking Point
I don't think so. The article is probably intended for the Nix community, so the author doesn't need to convince HN that something is going on. If as an outsider you are interested then you need to look into it yourself, the community has no obligation to make their internal conflicts legible to the outside world.
As an outsider myself, it certainly looks like something is going on as more than 20 Nixpkg maintainers left in a week: https://github.com/NixOS/nixpkgs/issues?q=label%3A%228.has%3...
- 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...
What are some alternatives?
emacs-overlay - Bleeding edge emacs overlay [maintainer=@adisbladis]
asdf - Extendable version manager with support for Ruby, Node.js, Elixir, Erlang & more
flake-utils-plus - Use Nix flakes without any fluff.
Home Manager using Nix - Manage a user environment using Nix [maintainer=@rycee]
nix-direnv - A fast, persistent use_nix/use_flake implementation for direnv [maintainer=@Mic92 / @bbenne10]
git-lfs - Git extension for versioning large files
solana-nix - The Solana CLI tools packaged up with Nix
easyeffects - Limiter, compressor, convolver, equalizer and auto volume and many other plugins for PipeWire applications
nixos - A fully automated replicable nixos configuration set
spack - A flexible package manager that supports multiple versions, configurations, platforms, and compilers.
elixir-ls - A frontend-independent IDE "smartness" server for Elixir. Implements the "Language Server Protocol" standard and provides debugger support via the "Debug Adapter Protocol"
waydroid - Waydroid uses a container-based approach to boot a full Android system on a regular GNU/Linux system like Ubuntu.