brew formula

[Raikerian]

Hey, thanks for this binary. Any chance you can set up brew formula for this?

[narugit]

@Raikerian
Hi, sorry for late response.
Yes. I want to add this tool in brew formula. However, I have never added tools in brew formula, so I need to investigate how to do.
Any supports are welcome :)

[mikemimik]

@narugit I was looking to see what requirements exist to create a brew formula and there are some good documents that exist for it.

I'd be happy to contribute a github workflow that does the versioning and release asset creation for you (I've done this before for some personal/work projects). Once that is in place, we could run the brew create command, along with some others, to create the contribution to the homebrew formula json.

(It might also be possible to create a github action to also do this homebrew formula update in an automatic way, so that any time a new version is created a new release/asset is created as well as a PR into the homebrew/core repository 🤔).

Reference: https://docs.brew.sh/Formula-Cookbook

[narugit]

@mikemimik
Thank you for helpful infomation and strong support!
Is following step is correct to publish as homebrew official package?

1. Create tarball
2. Create formula until audit and test pass
3. Create a pull request to official homebrew repository

I am curious about your workflow.
Could you create a pull request in this repository to add workflow?

[jvhaarst]

What @mikemimik means is that he can help you with setting up a workflow to create versioned releases of your code, thus checking off the "has a stable, tagged version" bullet in the requirements.

[narugit]

@jvhaarst
Thank you for pointing out my misunderstanding.
Finally I have found out that the workflow is for versioning to meat "has a stable, tagged version" requirement.
I will check that what I need to do before versioning.
If you know about it, I would appreciate it if you could tell me about it.

[jvhaarst]

On the main page of your repo you will find a "Releases" section, click on "Create a new release", and then you can tag the current state or a previous commit as a version.

[narugit]

@jvhaarst
Sorry for late response. I will ready to get started.

[narugit]

Tasks

Ref.: https://docs.brew.sh/Formula-Cookbook

• meets all our Acceptable Formulae requirements
• isn’t already in Homebrew (check brew search )
• isn’t already waiting to be merged (check the issue tracker)
• is still supported by upstream (i.e. doesn’t require extensive patching)
• has a stable, tagged version (i.e. isn’t just a GitHub repository with no versions)
• passes all brew audit --new-formula tests
• Before submitting a new formula make sure you read over our contribution guidelines.

[narugit]

• isn’t already in Homebrew (check brew search )

$ brew search smctemp
Error: No formulae or casks found for "smctemp".

[narugit]

• isn’t already waiting to be merged (check the issue tracker)

Yes. This is the first time.

[narugit]

• is still supported by upstream (i.e. doesn’t require extensive patching)

Yes

[jvhaarst]

Hi, do you need help with this ?
The main thing (without that nobody would be able to test locally), is to create a release.
You could just create a release of only the latest, or go back through the commits, and decide how big a change it was, and whether it was a change big enough to make it a new version.
Some ideas are here : https://nehckl0.medium.com/semver-and-calver-2-popular-software-versioning-schemes-96be80efe36
In the end it is your project, and you can decide how to version it.
But brew apparently needs and wants a version, so you will have to create a release, and add a version to it.

[narugit]

@jvhaarst
Thank you for kind support! May I ask a question?
Actually I am trying to write GitHub Actions workflow in .github/workflows/release.yml to create a release, but I have no idea to build each binary for x86_64 and arm64 with GitHub Actions.
Do I need to build by two binaries by myself and upload to release manually?

[jvhaarst]

I just had a look, and I couldn't find a way to compile arm64 from github actions, using the macos-latest runner (more info at https://docs.github.com/en/actions/using-github-hosted-runners/about-github-hosted-runners)

I did succeed in getting brew to create a functioning smctemp locally:

1. Create a release (click on Release, and follow the steps)
2. brew create [URL of release tar.gz], and change the recipe (see below)
3. HOMEBREW_NO_INSTALL_FROM_API=1 brew install --build-from-source --verbose --debug smctemp
4. brew audit --strict --online smctemp
5. After that you will have to follow the cookbook on how to add it to te brew recipe repo.
   (in the below code I have changed the test to use version as a variable, so make sure the version you publish is the same as referenced in the code)
   smtemp.rb:

class Smctemp < Formula
  desc "Check Temperature by using Apple System Management Control (Smc) tool"
  homepage "https://github.com/narugit/smctemp"
  url "https://github.com/narugit/smctemp/archive/refs/tags/v0.1.tar.gz"
  sha256 "986b2c1e8d6452a9f57342bf440e7bdbecf07983ce62dacfbe3fdcad0345f313"
  license "GPL-2.0-only"

  depends_on :macos

  def install
    system "make"
    bin.install "smctemp"
  end

  test do
    assert_match "#{version}", shell_output("#{bin}/smctemp -v")
  end
end

[jvhaarst]

The test is better written like this, otherwise you will get a warning :

  test do
    assert_match version.to_s, shell_output("#{bin}/smctemp -v")
  end

And a HEAD section would also be nice.