Support for Homebrew Formula

[tinder-maxwellelliott]

I have been investigating possibly allowing Mockolo to be installed via Homebrew. Are there any blockers to doing this? My strategy was to use the tarball creation script

./install-script.sh -s [source dir] -t mockolo -d [destination dir] -o [output filename]

To generate a tarball that the brew formula would install and then use homebrew's bin linking to make mockolo globally executable

[marciniwanicki]

It's a nice idea. I think there are no technical obstacles. On the other hand the formula might be not accepted for homebrew/core just yet. One of the requirements is for the formula to "be known". Maybe mockolo is already "known" - don't know :) Check out https://docs.brew.sh/Acceptable-Formulae for more info.

Another option would be to create a custom tap, maybe Uber org (https://github.com/uber) already has one (I haven't checked); in that case the formula could be pushed there. It's quite common solution and allows to quickly upstream new versions.

[tinder-maxwellelliott]

Can we just update the latest release with the output from ./install-script.sh -s [source dir] -t mockolo -d [destination dir] -o [output filename] (basically upload a tar.gz of the two files). If we do that our teams can at least make their own taps and start using mockolo via homebrew

[marciniwanicki]

Could work but it would probably skip few artifacts which brew implicitly include in the so called bottles (README.md, LICENSE etc.). Also, not sure if the output is brew-friendly, have the right folder structure (mockolo/<version>/bin etc).

A simple formula using swift build should allow the users to build the brew formula locally (when using brew install). It can also use prebuilt binary (bottle) if the link to the binary is also specified in the formula. You can make the bottle view brew bottle.. command, no need to package everything by hand.

I'd be interested to know how you use homebrew to distribute dev tools, from my experience it does not work well for bigger teams, quite tricky to enforce all dev and CI environments to use the right versions.

[tinder-maxwellelliott]

The issue with building from source is that it is very painful, can take up to 5 minutes! Other swift command line tools are able to support this so I believe it is possible for mockolo. Using brew would really open up the user base of this project.

As for version management yes you need to write more code to manage the versions as brew does not have the ability built it, is is pretty easy to script around it though

[elsh]

There's nothing preventing it; it's been on the todo list. Looks like brew cask might be an option for a binary only distribution if we go down that road. We can look into this soon.

[tinder-maxwellelliott]

Can I build a cask for you guys? Is that okay?

[elsh]

Can I build a cask for you guys? Is that okay?

Yes go ahead

[tinder-maxwellelliott]

Formula PR is here Homebrew/homebrew-core#51274

[tinder-maxwellelliott]

This will not work, building the formula takes too long on CI to even pass, we need to create a Cask. Can we make a new tagged release with a tar.gz of the built binaries attached to it? I need that tar.gz to create the cask https://github.com/Homebrew/homebrew-cask/blob/master/doc/development/adding_a_cask.md

[elsh]

Added https://github.com/uber/mockolo/releases/download/1.1.5/mockolo.tar.gz

[tinder-maxwellelliott]

Homebrew/homebrew-cask#78324

[elsh]

Fyi, the dylib in the same tarball, which is needed to run mockolo (and has to be in the same directory as the executable), requires xcode 11.0+ (swift 5.1+).

[tinder-maxwellelliott]

Okay I am attempting this again, Homebrew/homebrew-core#51274 , I am not sure the build will finish in time, sometimes the swift build times out

[elsh]

Thanks for pushing the pr. Looks like all checks have passed, pending a final review.

[tinder-maxwellelliott]

Do you want to comment on that PR, I am not sure when they will get around to looking at it

[elsh]

done

…

On Wed, Mar 11, 2020 at 5:34 PM Maxwell Elliott ***@***.***> wrote: Do you want to comment on that PR, I am not sure when they will get around to looking at it — You are receiving this because you commented. Reply to this email directly, view it on GitHub <https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_uber_mockolo_issues_97-23issuecomment-2D597947890&d=DwMCaQ&c=r2dcLCtU9q6n0vrtnDw9vg&r=sTqCC7cTwGN2QCw_Vq6sKQ&m=txt3XLy2Njco4q9WIERWY2BNj_kl9kP11qCGbqTY7Mk&s=dFnjmbZARdhuDmR1zMJCG3lDHLq3qeZSXa_rGcVbbHg&e=>, or unsubscribe <https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_notifications_unsubscribe-2Dauth_AAUG5PEW3BO7FG442P2JMQDRHAU25ANCNFSM4LBNKNWQ&d=DwMCaQ&c=r2dcLCtU9q6n0vrtnDw9vg&r=sTqCC7cTwGN2QCw_Vq6sKQ&m=txt3XLy2Njco4q9WIERWY2BNj_kl9kP11qCGbqTY7Mk&s=lyFPJ8wnmwiLLT1tKzbfm0p2HcD6CW3qXjV8csvjgGE&e=> .

[elsh]

🎉