Mac OS: Support brew installation for Harmony

[jacksteroo]

Description

Package our binary, for brew. Or in brew terms, "Bottle Harmony One binaries into Brew Casks!". For example, brew install harmony-one should initiate installation of Harmony binaries alongside all the dependencies. Also allow the installation to be pinned to a certain version.

Context

This encourages ease of development and testing, and further helps with decentralizing the ecosystem. See Brew documentation for more info.

Acceptance Criteria

• Submit the latest Harmony binaries into the brew repo
• Ensure the setup and installation abides by Harmony and brew guidelines (e.g. permissions, install path, etc.)
• Document the steps necessary to post the latest builds to the brew repo
• Submit the changes with brew (and Harmony if needed) and review with the Harmony team

Reward

USD $500 (in ONEs)

[cylim]

What is suppose to pack into the bottle? The Harmony CLI?

[cylim]

Due to the harmony-one/go-sdk doesn't met minimum requirements for publish to Homebrew, I am using harmony-one/harmony as the base.

According the Homebrew, Notable enough repo should have >30 forks, >30 watchers and >75 stars.

Besides that, when running hmy <command>, it is showing a warning message, which should be related to
harmony-one/go-sdk#256 (comment)

Warning: Using outdated version. Redownload to upgrade to v417-bc3f026

A new formula PR is created for homebrew/core: Homebrew/homebrew-core#85856.
Documents for updating the formula is not created yet, will wait for the PR approval.
This might work for Linux too, I can't be sure about it due to I didn't test it on any Linux distros.

[cylim]

@LeoHChen
May I know what is the reasons why the latest harmony-one/go-sdk github actions removed the ARM64 build. harmony-one/go-sdk@v1.2.6...v1.2.7
I can't debugging the homebrew formula for arm64 due to I don't have the required device for testing, so I have set the arch to x86 only, but homebrew team is asking about it.

[cylim]

PR for a bug related to Go 1.17 on MacOS: harmony-one/go-sdk#270

Need to figure out what is the issues with arm64, unfortunately, I don't have a M1 Macbook.

[gitcoinbot]

Issue Status: 1. Open 2. Started 3. Submitted 4. Done

---

This issue now has a funding of 3426.2931 ONE (502.66 USD @ $0.15/ONE) attached to it.

• If you would like to work on this issue you can 'start work' on the Gitcoin Issue Details page.
• Want to chip in? Add your own contribution here.
• Questions? Checkout Gitcoin Help or the Gitcoin's Discord
• $4,566,245.58 more funded OSS Work available on the Gitcoin Issue Explorer

[gitcoinbot]

Issue Status: 1. Open 2. Started 3. Submitted 4. Done

---

Work has been started.

These users each claimed they can complete the work by 265 years, 1 month from now.
Please review their action plans below:

1) cylim has started work.

1. Create Homebrew Bottle
2. Fix bugs for Linux Build (Yes, homebrew can be use in Linux now)
3. Fix bugs in Go SDK for Go 1.17 and arm64 Mac
4. Get PR approval from Homebrew
5. Create Doc for Harmony about how to upgrade dependencies and main package

• One thing, it will be using Harmony repo as main package and Go-SDK as dependecies due to Go-SDK repo doesn't met requirement for publishing on Homebrew.

We can discuss about it at #69

Learn more on the Gitcoin Issue Details page.

[cylim]

@LeoHChen just in case if you didn't saw my comments ealier, I had summarize to three items.

Questions/Note

1. Main Package is using Harmony not go-sdk - The go-sdk doesn't met minimum requirements (>30 forks, >30 watchers and >75 stars)
2. Go 1.17 Support - Pending PR review (fix(mod): update fatih/color for go 1.17 macos go-sdk#270)
3. ARM64 Support - Pending Feedback from Go-sdk (arm64 macos  go-sdk#271)

[LeoHChen]

@cylim to package the harmony node program, not just the hmycli

[cylim]

@LeoHChen which repo is for the node?
The formula has included harmony, bls, mcl and go-sdk to ensure it is working correctly.

[LeoHChen]

@cylim https://github.com/harmony-one/harmony

[LeoHChen]

for go-sdk, I am asking for our dev community support to have more star, and forks.

[cylim]

@LeoHChen All good. The 4 dependencies are all included in one formula.
It is just whether we want to use harmony or go-sdk as the base, because the upgrading process is slightly different.
I would prefer to use go-sdk as the base, because the hmy cli command is exposed from go-sdk. which it required (>30 forks, >30 watchers and >75 stars) to become the base of a brew formula. 😄

[GraoMelo]

@jacksteroo

your project has many conflicting dependencies.

not compilede for mac os.. then nothing of brew.

` honnef.co/go/tools v0.0.1-2020.1.5 // indirect
)

replace github.com/ethereum/go-ethereum => github.com/ethereum/go-ethereum v1.9.9`

what?

or better:

https://github.com/harmony-one/mcl.git
compile only windows.

https://github.com/harmony-one/bls.git
compile only windows too.

so how to create a precompiled package for mac os if it doesnt compile?

[cylim]

@GraoMelo The project had passed CI/CD and successfully installed in different MacOS and Linux.

The issues we are facing now is there is too many hardcoded path in the Makefile or script files, and Homebrew prefer to do it the Go Module way.

Homebrew/homebrew-core#87031

[klngrs]

@jacksteroo - Figured I'd get my feet wet looking at this.

In the spirit of eliminating manual processes on the part of the Harmony core team or manual processes with every release, what are your thoughts on:

Edit the harmony release github action to:

1. Fork/Checkout homebrew core
2. Create a branch w/ the name of the Harmony release number
3. Edit the homebrew formula with the updated release info / shas
4. Submit a PR to homebrew in an automated fashion

[gitcoinbot]

Issue Status: 1. Open 2. Started 3. Submitted 4. Done

---

Work for 3426.2931 ONE (1077.45 USD @ $0.34/ONE) has been submitted by:

---

• Learn more on the Gitcoin Issue Details page
• Want to chip in? Add your own contribution here.
• Questions? Checkout Gitcoin Help or the Gitcoin's Discord
• $6,933,857.73 more funded OSS Work available on the Gitcoin Issue Explorer