nix-config VS homebrew-core

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

$ brew info eza ==> eza: stable 0.18.13 (bottled) Modern, maintained replacement for ls https://github.com/eza-community/eza Not installed From: https://github.com/Homebrew/homebrew-core/blob/HEAD/Formula/e/eza.rb License: MIT ==> Dependencies Build: pandoc ✘, pkg-config ✔, rust ✘ Required: libgit2 ✘ ==> Analytics install: 12,792 (30 days), 38,295 (90 days), 68,375 (365 days) install-on-request: 12,790 (30 days), 38,293 (90 days), 68,375 (365 days) build-error: 0 (30 days)

Is disabling the compromised repo the typical GitHub policy? My concern is there are monorepos used by package managers, like brew, that are a collection of thousands of projects [1]. These monorepos seem like a prime target for attack and if GitHub disables one because a malicious commit was merged then you've taken down an entire ecosystem.

[1] https://github.com/Homebrew/homebrew-core

> Correct. Though we do not appear to be affected, this revert was done out of an abundance of caution.

[1] https://github.com/Homebrew/homebrew-core/pull/167512

> right, but now you know even less about your setup when you some roadblock

This is the same with a binary though. And with homebrew, you can't follow patches or flags used or if they change.

- https://github.com/Homebrew/homebrew-core/blob/c964ad7fa53ad...

definitely be careful about using fortune in a corporate environment or public space if you don't know what dat files you are using or you might just get an extremely unwelcome surprise.

I was practicing a presentation and used to use "fortune" all the time. I forget exactly what it output but I remember being absolutely mortified about what could have happened if that had popped up during an internal company tech talk.

Kudos to brew for keeping unsuspecting people safe

https://github.com/Homebrew/homebrew-core/commit/3fb3c4c3e55...

I'm sorry to be asking this as I find it a bit silly, but it's blocking my PR [3], so could a few of you star the project on Github [1] to get my PR to run?

[1] https://github.com/laktak/chkbit-py

[2] https://brew.sh

[3] https://github.com/Homebrew/homebrew-core/pull/160018