nix-config VS nixpkgs

All the resources mentioned in other comments are pretty good, but mostly they are unofficial. The official NixOS wiki is very outdated and unmaintained. You will have better luck reading other people’s configurations, nixpkgs source code and GitHub issues. For the nix language the official wiki is a nice reference https://nixos.org/manual/nix/stable/language/index.html. This configuration is a great starting point https://github.com/Misterio77/nix-config for learning by example. It covers most of what you may need, although bootstrapping your own config is quite rough. You may want to take a look at https://github.com/Misterio77/nix-starter-configs. It’s very basic and should be simple to understand and improve.

Yes. E.g. some guy's config with 6 different machines[1]: multiple desktops, laptops, servers, a Raspberry Pi, and a VPS. That's a rather advanced use of Nix for configuration, but definitely shows what it's capable of.

[1] https://github.com/Misterio77/nix-config

https://github.com/Misterio77/nix-config/blob/main/hosts/celaeno/services/hydra/lib/release-host-branch.nix https://github.com/Misterio77/nix-config/blob/main/hosts/celaeno/services/hydra/default.nix#L39

Implementation: https://github.com/Misterio77/nix-config/blob/main/pkgs/fetch-packwiz-pack/default.nix

the one i reference all the time is https://github.com/Misterio77/nix-config

I believe Misterio77's does use it in his config.

I reuse the same btrfs logic on all my computers, including a RPi: https://github.com/Misterio77/nix-config/blob/main/hosts/common/btrfs-optin-persistence.nix

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...

https://github.com/NixOS/nixpkgs/commits?author=neon-sunset

I see two signers in the top 6 displayed on https://github.com/NixOS/nixpkgs/graphs/contributors

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,

```

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...

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...

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

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...