Is this a BUG REPORT or FEATURE REQUEST? (choose one): feature request
We currently have a brew _cask_ installer, which installs from a pre-built binary. However, we can create a real brew formula for minikube now that we no longer include (and therefore don't cross build) localkube with go-bindata.
I think the formula should be pretty straightforward and would be very similar to existing go formula.
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale
Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten
/remove-lifecycle stale
@r2d4 , I think we can close this issue right?
I can see cask file https://github.com/caskroom/homebrew-cask/blob/master/Casks/minikube.rb .
Currently the cask just downloads the prebuilt binary. Now that we don't package localkube anymore, we can just build from source and have a real _brew_ formula instead of just a cask.
If no one is working on creating a build formulae I can propose myself as an assignee.. Have a recent experience generating a formulae for another tool.
Still needed.
Still needed.
Currently we ship the _same_ Linux binary everywhere: raw, tgz, deb, rpm
We might do the same for Darwin, that is leave it as a brew "cask" (binary)
it okay if I have a crack at this?
it okay if I have a crack at this?
yes you could have this issue ! :)
I've opened a PR for a minikube formula: https://github.com/Homebrew/homebrew-core/pull/45603
Before we close this, we'll need to insure that our release scripts release to brew rather than cask:
@commitay @issyl0 - are either of you interested in taking a crack at updating our release scripts?
I thought distros was supposed to pull (new releases) rather than push (from vendor) ? Especially if it is no longer our binary, but something they build. But not sure how Brew normally operates.
@tstromberg I don't currently have enough spare time to help with this bigger piece of work, sorry!
Most helpful comment
I've opened a PR for a
minikubeformula: https://github.com/Homebrew/homebrew-core/pull/45603