this post was submitted on 02 Jan 2024
91 points (87.0% liked)
Linux
48697 readers
1392 users here now
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Rules
- Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
- No misinformation
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I sometimes write a flake with those 4 lines of Nix code, and it comes out just messy enough that tbh I'm happier adding an input to handle that. But I recently learned that the nixpkgs flake exports the
lib.*
helpers throughnixpkgs.lib
(as opposed tonixpkgs.legacyPackages.${system}.lib
) so you can call helpers before specifying a system. Andnixpkgs.lib.genAttrs
is kinda close enough toflake-utils.lib.eachSystem
that it might make a better solution.Like where with flake-utils you would write,
Instead you can use
genAttrs
,It's more verbose, but it makes the structure of outputs more transparent.
Saving the dependency is pretty big since each flake you import will bring along its jungle of dependencies now in your downstream project. I can’t think of a use case where < 10 lines is worth a dependency—especially since as you noted,
lib
has the glue right there for you to put it all together.