homebrew-portable-ruby VS homebrew-bundle

Yes, they have their own special ruby build made for portability.

==> Downloading https://github.com/Homebrew/homebrew-portable-ruby/releases/download/2.6.8/portable-ruby-2.6.8.x86_64_linux.bottle.tar.gz

I maintain a Brewfile (https://github.com/Homebrew/homebrew-bundle) which contains the majority of the non-project specific applications that I like to install on any new Mac:

https://github.com/jonahgeorge/dotfiles/tree/main

What's really nice is the `cask` & `mas` keywords allow you to install .dmg files & directly from the App Store.

---

While its not included in there yet, I've been experimenting with maintaining a private Homebrew tap which contains my ~/bin directory as opposed to shell aliases.

> 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](https://github.com/Homebrew/homebrew-bundle) let’s 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 (with a script that maintains symlinks to config files in e.g. ~/Library) works well enough for my use.

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.

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

You should checkout Homebrew bundle and create a Brewfile instead. That will let you install both stuff from brew, casks and Mac AppStore apps in one go.

If you use brew bundle and create your own Brewfile, you can store this with your personal dot files and automate bootstrapping (auto-installing all your system tools) a new or recently reformatted Mac by including auto-trader-pro in your Brewfile.

And if you're already loving Homebrew, definitely check out Homebrew Bundle!

If you like homebrew, definitely give homebrew bundle a whirl if you haven't already