homebrew-bundle

> It's strange that people are so against declarative systems, or even file-based OS configuration. When I get my new Macbook I was up-and-running within a few minutes. I can't imagine maintaining a list of brews I need to re-install just to set up everything + my configs + everything else. I haven’t had time to try Nix yet, but HomeBrew does have a declarative-ish workflow that I’ve been using for years: Brew Bundle [1] lets you have a plaintext file listing all packages you want installed on your system. Add a line for stuff you want installed, delete a line for stuff you want removed, invoke it the right way and it will install/remove packages until your system matches the list. The initial list can be generated by “brew bundle dump” or something like that. For configuration, I find that a normal dotfile repo cloned into my ~/.config (

Brew supports dumping installed things into a brewfile: https://github.com/Homebrew/homebrew-bundle I was using text files before as well to manage it.

Assuming everyone's on a Mac, I'm actually surprised there isn't that much use of something like homebrew-bundle[1]. It's definitely nicer to have your tooling run natively rather than, say, trying to wrap everything in Docker, or trying to get everybody on board with nix or guix. I think the only real issue here is that you can't really pin to specific versions unless a formula exists, and there is no guarantee that a formula with a pinned version will stick around because homebrew likes to stay lean. So to that extent it can still be unclear what version of software someone is running on after enough time. [1]https://github.com/Homebrew/homebrew-bundle/