Homebrew Support

[bsrz]

Homebrew has been the de facto distribution model for many apps and binaries for some time now.

The idea that I have to install tuist through a curl->bash process and have to give it my password during installation is really high risk and really shouldn't be required.

Codecov went through this exact issue a couple years ago and brought down many companies and CI services, forcing everyone to cycle keys and passwords in an attempt to stop the bleeding.

[bsrz]

Merging a formulae in the main homebrew repo might not be an option but hosting a formulae is pretty simple: https://docs.brew.sh/How-to-Create-and-Maintain-a-Tap

[vanyauhalin]

And an official cask is on for 3.18.0! (Just informational, cask is the recommended way to distribute binaries with homebrew, Formulas are for building binaries usually)

I'm sorry, but I couldn't find you on either the core team or the contributors' list. Therefore, I'm having trouble understanding why this is considered an official cask.

I also agree with @carlocab that this is a formula, not a cask (Homebrew/homebrew-cask#145456 (comment)). Below, I will quote from the Homebrew documentation and note that the homebrew-core repository contains many formulas distributed as binaries without needing a building stage.

App is both open-source and CLI-only (i.e. it only uses the binary artifact). In that case, and in the spirit of deduplication, submit it first to homebrew/core as a formula that builds from source. If it is rejected, you may then try again as a cask (link to the issue from your pull request so we can see the discussion and reasoning for rejection).

[danieleformichelli]

I think official meaning that has been merged in the official homebrew-cask :D

[danibachar]

Indeed. When i meant official i meant it is part of the homebrew/cask repo. Im not a maintainer nor any official officer of any organization (:

Your tap is great, and maybe it worth adding a tap repo under the Tuist Github org?!

it will not be accepted to the official homebrew/core repo as it is a universal binary. And according to the discussion I opened they will also not accept pre-build binaries.

[vanyauhalin]

Indeed. When i meant official i meant it is part of the homebrew/cask repo. Im not a maintainer nor any official officer of any organization (:

Your tap is great, and maybe it worth adding a tap repo under the Tuist Github org?!

it will not be accepted to the official homebrew/core repo as it is a universal binary. And according to the discussion I opened they will also not accept pre-build binaries.

Thank you for your kind words. I would be delighted if the core team could support installation via Homebrew, but unfortunately, they abandoned that idea many years ago, so... As for my tap, I'll try to add a build stage to bring it more in line with Homebrew's guidelines.

[vanyauhalin]

@danibachar

Finally, I added a build stage for the formula. I also added the latest versions with aliases, so you can easily change the current version of Tuist.

[jeffremer]

I don't have strong opinions on the curl > bash installer vs. Homebrew, other than the obvious benefits that @bsrz pointed out. However, a teammate just ran into a surprising issue. He didn't follow my instructions to use the curl > bash installer, so when he installed it via Homebrew it installed a specific version that varied from the version we have pinned in the .tuist-version file that normally tuistenv respects. The homebrew version didn't automatically install the pinned version.

We're currently committing some of the derived/generated code - granted we should probably stop doing that - but he was surprised to see changes in derived source code upon generation because of the variation between what we had pinned and the newer version he installed via Homebrew.

[danibachar]

Fair point, we have a bunch of cli tools we are using, and we use Homebrew and the related Brewfile/.lock for versioning across teams... (I also don't have a strong opinion on how to maintain or keep cli tools versioning, the fact is that homebrew is what we use)
I don't expect Tuist team to maintain a tap/cask though... Just notified about the supported in cask

[AllDmeat]

Would be great to switch to homebrew installation, as it would simplify First project run for newcomers and CI workflows as well — simple brew bundle will do all the work.
But we are pinning to specific Tuist version using .tuist-version, and if I got it correct, brew cask install only tuist itself, not tuistenv.
Any plans to make a formula/cask for tuistenv?

[vanyauhalin]

@pepicrft, it would be an honor for me!

I attempted to transfer the repository to the organization, but unfortunately, I currently don't have sufficient privileges to do so.

You don't have the permission to create public repositories on tuist

Could you please grant me the permission to create public repositories in the organization?

[vanyauhalin]

Another option is to transfer the repository to your personal account. I'll do what's most convenient for you.

[pepicrft]

Could you transfer it to pepicrft? I'll transfer it from there.

[vanyauhalin]

Done.

[pepicrft]

Thanks a lot @vanyauhalin 🙏🏼