manix VS nixpkgs

I found this a few weeks ago: https://github.com/mlvzk/manix

I suggest installing manix it is available through nix and let's you search multiple sources (home-manager nix ect).

One good example of what Nix documentation could be is this guy's "concept art" of what Nix function documentation could look like. Just being able to generate JSON schemas for Nix functions somehow would be really cool. (The information is there, just hidden in either function argument specifiers { path, text } or in comments like in nixpkgs' lib/lists.nix.) Stuff like the manix doc searcher is really cool and desperately needed. When I get some free time I want to try autogenerating Nix function schemas from their declarations, or even autogenerating schemas for flakes and the like from their checking in C++.

There is also a CLI: https://github.com/mlvzk/manix

I use manix for that purpose, it gives you a quick way of search for config options directly from the command line, as opposed to opening up the man page and searching inside that: https://github.com/mlvzk/manix

This will drop you into a shell where `tracexec` is installed.

[1]: https://github.com/NixOS/nixpkgs/pull/310158

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