3 ms·
You‘re right, it‘s best managed inside of MacPorts, which allows you to install specific versions of packages and switch between them easily!
by wwalexander 3y ago
You‘re right, it‘s best managed inside of MacPorts, which allows you to install specific versions of packages and switch between them easily!
- whalesalad 3y agotil macports still exists
- wwalexander 3y agoIt not only exists but is vastly superior to Homebrew.
- hnlmorg 3y agoYou can do that with homebrew too. But in the case of Terraform, where you can have developers on Windows and macOS and CI/CD pipeines based on Debian/Ubuntu/CentOS/Alpine/etc, it's handy having everyone use the same tool for managing Terraform versions. It's just like how you wouldn't have different people manage the same Python codebase with different package managers. You agree on the standard for that business or project and have every instantiation of that project follow that same standard.
- wwalexander 3y agoI definitely agree overall. My last job was standardized on Homebrew and used tfswitch; I personally translated to MacPorts but I do agree that tying a project to a specific package manager (and thus OS, etc.) isn’t advisable.
- soraminazuki 3y agoI think Nix is better suited for that kind of thing. You can specify multiple versions of packages and expose them on a per-project basis. It eliminates the need to switch packages globally.