neovim-nightly-overlay VS nixpkgs

Don't use nix build to build neovim. Add an overlay to your flake and use home-manager programs.neovim option. It will automatically compile latest neovim for you when you rebuild the configuration.

Relevant? https://github.com/nix-community/neovim-nightly-overlay/issues/164

You can use the overlay

You can use the nix-community overlay or the flake.

-- SNIP -- nixpkgs.overlays = [ (import (builtins.fetchTarball { url = https://github.com/nix-community/neovim-nightly-overlay/archive/master.tar.gz; })) ]; -- SNIP -- programs = { neovim = { enable = true; package = pkgs.neovim-nightly; configure = { customRC = (builtins.readFile ./init.vim); }; }; }; -- SNIP --

There is no centralised way of sharing user packages. But you can create package overlays or use sombodys overlays if you can find them (e.g. I use neovim nightly overlay).

However, then you run into this issue.

Ok so I am using https://github.com/nix-community/neovim-nightly-overlay to build neovim from source in order to use the latest features. Does anyone know of any way I can specify makeflags, such as march=native or O3 when building the package? Thanks so much for your help.

I'm using https://github.com/nix-community/neovim-nightly-overlay which does get Neovim 0.5 running, it's just not using my init.lua properly, picking up its own init.vim instead.

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