Fix Homebrew release

[bolinfest]

I believe the Homebrew release is not being done correctly.

For macOS, we release a universal binary:

dotslash/.github/workflows/release.yml

Lines 22 to 42 in 92fe071

	macos:
	needs: create-release
	runs-on: macos-13
	timeout-minutes: 30
	steps:
	- uses: actions/checkout@v4
	- uses: dtolnay/rust-toolchain@stable
	with:
	targets: aarch64-apple-darwin,x86_64-apple-darwin
	- run: cargo test
	- run: cargo clippy
	- run: cargo build --release --target aarch64-apple-darwin
	- run: cargo build --release --target x86_64-apple-darwin
	- run: lipo -create -output dotslash target/aarch64-apple-darwin/release/dotslash target/x86_64-apple-darwin/release/dotslash
	- run: tar -czvf "dotslash-macos.${GITHUB_REF#refs/tags/}.tar.gz" dotslash
	shell: bash
	- name: upload release
	env:
	GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
	shell: bash
	run: gh release upload "${GITHUB_REF#refs/tags/}" "dotslash-macos.${GITHUB_REF#refs/tags/}.tar.gz"

As explained here:

dotslash/website/docs/installation.md

Lines 9 to 18 in 92fe071

	:::note
	On macOS, we **strongly** recommend running DotSlash as a
	[Universal Binary](https://developer.apple.com/documentation/apple-silicon/building-a-universal-macos-binary)
	rather than an x86 or ARM64 binary. If an x86 binary is running under
	[Rosetta](https://developer.apple.com/documentation/apple-silicon/about-the-rosetta-translation-environment)
	on Apple Silicon and ends up spawning `dotslash`, then for consistency with the
	parent process, this will ensure that the `macos-x86_64` artifact will be run.
	:::

But based on my read of how the Brew formula was created:

Homebrew/homebrew-core@8e53cba

and the subsequent changes to that file:

https://github.com/Homebrew/homebrew-core/commits/master/Formula/d/dotslash.rb

It looks like it is doing a simple cargo install, so it is not creating a universal binary.

Can we work with the Homebrew maintainers to fix this?

[abhinav]

I don't know if this is still accurate, but as of Homebrew/brew#10307 and https://github.com/orgs/Homebrew/discussions/412, Homebrew does not support bottling universal binaries.

[alerque]

I believe the Homebrew release is not being done correctly.

According to the detailed explanation given in the discussions linked above the Homebrew maintainers disagree with you. TL;DR They deliberately don't support universal binaries because it is problematic to cross-compile across the whole ecosystem and brew itself is specifically designed to run and install things that run on the host local system, not install apps that run on something else. If you are layering emulation layers that's your problem. You'll get binaries optimized for whatever platform brew itself is running on. That this trickles down to the binaries fetched by dotslash is unsurprising.