Yes, I want them. My NixOS configuration is sandboxed (defaults to true anyway). I was happy with using dnf, but sick of having to use multiple package managers. I also didn’t like how contributing to Fedora had a lot of cognitive overhead, so I use NixOS now. One package manager to rule them all. I have access to expressions, I do ocassionally read them, so I trust them. And if there’s no apps on Nix, I write expressions and contribute to the repo.
Irritate the core maintainers and they will teach you just like Mr Miyagi. /s
Honestly, contributing to nixpkgs isn’t that hard. You just have to refer other expression files. This guide is probably one of the most well-written guides I’ve come across.
Just a word of advice, while cloning NixOS/nixpkgs, set --depth to somewhere between 1 to 10. It’s a pretty large repository, and you just want to have the last ten git logs at most.
As someone who struggled quite a bit to learn Nix, I’d say start small. Install Nix the package manager on any old distro you’re familiar with and play with standalone Home Manager. Enable one program here and there, have it manage your shells and CLI apps, set environment variables and write files. It’s something you can immediately see the effects of and feels pretty rewarding, so I think it’s a great place to start.
I also happened upon this video series a few days ago and it’s a great resource, easy to parse and walks you through not only the basics but how to look around and investigate in the REPL when you want to figure something out.
No, I have before, but I don’t anymore.
No.
Yes, I want them. My NixOS configuration is sandboxed (defaults to true anyway). I was happy with using
dnf, but sick of having to use multiple package managers. I also didn’t like how contributing to Fedora had a lot of cognitive overhead, so I use NixOS now. One package manager to rule them all. I have access to expressions, I do ocassionally read them, so I trust them. And if there’s no apps on Nix, I write expressions and contribute to the repo.Is it possible to learn this power?
Irritate the core maintainers and they will teach you just like Mr Miyagi. /s
Honestly, contributing to nixpkgs isn’t that hard. You just have to refer other expression files. This guide is probably one of the most well-written guides I’ve come across.
Just a word of advice, while cloning NixOS/nixpkgs, set
--depthto somewhere between 1 to 10. It’s a pretty large repository, and you just want to have the last ten git logs at most.Side note, I wish yesterday me had read this before cloning the full 4 gigs lol
As someone who struggled quite a bit to learn Nix, I’d say start small. Install Nix the package manager on any old distro you’re familiar with and play with standalone Home Manager. Enable one program here and there, have it manage your shells and CLI apps, set environment variables and write files. It’s something you can immediately see the effects of and feels pretty rewarding, so I think it’s a great place to start.
I also happened upon this video series a few days ago and it’s a great resource, easy to parse and walks you through not only the basics but how to look around and investigate in the REPL when you want to figure something out.
Here is an alternative Piped link(s):
this video series
Piped is a privacy-respecting open-source alternative frontend to YouTube.
I’m open-source; check me out at GitHub.