shaka-packager 3.4.0 (new cask)

[garnajee]

Important: Do not tick a checkbox if you haven’t performed its action. Honesty is indispensable for a smooth review process.

In the following questions <cask> is the token of the cask you're submitting.

After making any changes to a cask, existing or new, verify:

• The submission is for a stable version or documented exception.
• brew audit --cask --online <cask> is error-free.
• brew style --fix <cask> reports no offenses.

Additionally, if adding a new cask:

• Named the cask according to the token reference.
• Checked the cask was not already refused (add your cask's name to the end of the search field).
• brew audit --cask --new <cask> worked successfully.
• HOMEBREW_NO_INSTALL_FROM_API=1 brew install --cask <cask> worked successfully.
• brew uninstall --cask <cask> worked successfully.

---

[daeho-ro]

I left some comment.
I saw that there are intel version too, so you may add it with arch stanza.

[garnajee]

Thanks for your feedback! Regarding the sha256 line, since we now have both Intel and ARM support for the shaka-packager binary, I'm not entirely sure how to handle this part. Do we need to include two separate sha256 checksums? If so, how?
edit: i found how to do it.

I hope this modification works for you, but feel free to let me know if you have any suggestions on how to handle this.

[daeho-ro]

caveats is allowed only for the Homebrew specfic one, and yours are quite general so I deleted and squash your commits.

[daeho-ro]

Hm... signing problem only for intel. Is this can be fixed? Or should we go only with arm?

[garnajee]

Hm... signing problem only for intel. Is this can be fixed? Or should we go only with arm?

Well i don't know...
I just sha256sum packager-osx-x64.

I only did arm64 at first, because all the new Macs (since M1 2020) are equipped with arm chips. that was why I chose it.