NUR VS nixpkgs

So first, I'm a bit confused about AUR. I'm not aware of what you're describing. I heard about AUR-like repo for Nix (called NUR https://github.com/nix-community/NUR).

You need to use nur

Hi, I'm the author of the PR :) I uploaded it to NUR precisely so that it would be available sooner. However, as I wrote in the thread yesterday, as of this PR one of the components the package was relying on was deprecated. I'm still trying to make it work again using the new buildFHSEnv. However, if you're running 22.11 or haven't updated your local version of nixpkgs beyond that PR, it should still work.

Apart from nixpkgs having many packages, there is also NUR which has even more stuff.

You might also want to publish your sarc utility on NUR, https://nur.nix-community.org/

nur = import (builtins.fetchTarball "https://github.com/nix-community/NUR/archive/master.tar.gz") {

Nix also has the NUR. I have never needed to use it, while when I used arch I had many AUR packages.

Follow the NUR installation instructions and it should be in pkgs.nur.repos.arc.packages.nvidia-patch.

As for the community repo, there's nur but only 120 people use it.. I think the reason nixpkgs is so big is that the community is pretty accepting of accepting loads of different packages.

Some common options for the first: - your own git repo - your own flake (a specially constructed and easy to consume git repo) - something like NUR

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