comma VS nixpkgs

Nowadays, I tend to try things out with comma, then add them to my configuration for later use. Some tools are not even installed in my systems because I use them so infrequently - opening a terminal and running , freecad is basically as easy as actually having it installed.

There's a version of this approach that uses nix-index to figure out which package a command is in called comma: https://github.com/nix-community/comma

Relatedly, check out comma. It's basically a shortcut prefix command that will search packages for the binary you want to run (via nix-index), and gives you an interactive choice if there are multiple. Which package was drill in again? No matter, I'll just prefix a comma :)

https://github.com/nix-community/comma

this + if you want to run a command automatically I suggest comma

Yeah dude. Emphemeral installs are a feature, not a bug. Similar vein is , https://github.com/nix-community/comma

You're looking for https://github.com/nix-community/comma

One of the nicest tools is comma. https://github.com/Shopify/comma. It's just a light weight wrapper around searching nix-pkgs and running something, but it sure makes a lot of things easier when you're sharing somebody else's laptop.

If you want to test out some program, I would STRONGLY recommend using nix-shell -p . This will create temporary environment, that will allow you to test out the package. You can also check out comma.

I love using Shopifys comma tool https://github.com/Shopify/comma cause it's so useful for just small programs that u need to run once and then forget about them

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