meshtastic 2.7.8 (new formula)

[yunhao-jiang]

---

• Have you followed the guidelines for contributing?
• Have you ensured that your commits follow the commit style guide?
• Have you checked that there aren't other open pull requests for the same formula update/change?
• Have you built your formula locally with HOMEBREW_NO_INSTALL_FROM_API=1 brew install --build-from-source <formula>?
• Is your test running fine brew test <formula>?
• Does your build pass brew audit --strict <formula> (after doing HOMEBREW_NO_INSTALL_FROM_API=1 brew install --build-from-source <formula>)? If this is a new formula, does it pass brew audit --new <formula>?

---

• AI was used to generate or assist with generating this PR. Please specify below how you used AI to help you, and what steps you have taken to manually verify the changes.

---

First-time contributing to homebrew-core and there might be places I've missed (more test required, etc.?), please let me know! Thanks

The original repo: https://github.com/meshtastic/python

[GunniBusch]

Suggested change

	depends_on "python@3.14"
	depends_on "certifi" => :no_linkage
	depends_on "python@3.14"
	pypi_packages exclude_packages: "certifi"

Also remove rust dependency as that is only require for certifi, no?

and then rerun brew update-python-resources. Might need to rerun brew style --fix too

[GunniBusch]

You forgot to run brew update-python-resources since the certifiressource is still present (and thus duplicated)

[GunniBusch]

so yeah, you do need rust but for bleak

[yunhao-jiang]

Thanks! Just added it back! Looks like I should test on Linux in addition to macOS to make sure everything builds haha. A little different from contributing to the casks repo. Thanks a lot!

One question however -- it seems bleak does not need rust on macOS, should I keep it like this? (only Linux dependency requires rust but not macOS) OR should I revert back to my original where everywhere requires rust (removes the certifi dependency and also let that build from the source)

[GunniBusch]

Also you should indeed add more tests, as version test can be used together with other tests (like as an addition) but not as the only test. Testing is here only so we know that compilation and other build steps where successful (by running the binary).

See https://docs.brew.sh/Formula-Cookbook#add-a-test-to-the-formula

[yunhao-jiang]

For this part, I'm having a little hard time as this software controls an external hardware. If no external hardware is connected, it would be difficult to test the functionality. Do you have any recommendations in such case? (i.e. should I test for failure instead? like meshtastic --info should return False)

Thanks!

[GunniBusch]

i.e. should I test for failure instead?

Yes for example if it needs to connect to a device, try to run a command that would only work if it is connected, and check that it successfully failed.

[github-actions]

Thanks for contributing to Homebrew! 🎉 It looks like you're having trouble with a CI failure. See our contribution guide for help. You may be most interested in the section on dealing with CI failures. You can find the CI logs in the Checks tab of your pull request.

[GunniBusch]

PyObjC is only relevant on macOS.

so add below the depends_on:

  on_macos do
    depends_on "llvm" => :build if DevelopmentTools.clang_build_version <= 1699
  end

  fails_with :clang do
    build 1699
    cause "pyobjc-core uses `-fdisable-block-signature-string`"
  end

and replace your install block with

    if OS.mac?
      ENV.append_to_cflags "-isysroot #{MacOS.sdk_path}"
    else
      without = resources.filter_map { |r| r.name if r.name.start_with?("pyobjc") }
    end
    virtualenv_install_with_resources(without:)