Publish MacOS package to homebrew about notepadnext HOT 9 CLOSED

This was brought up previously in #138

Much of what I said in that issue still holds, though I'm a bit more apt to consider additional ways to publish the application now that I've automated much of the release process. I have no way to test/debug/support any issues with MacOS or publishing it to Homebrew or know the level of effort involved. If someone was willing to implement/own the process to publish it to Homebrew I'd consider it as long as it does not add any extra burden to publishing releases (e.g. meaning it was integrated into the CI process).

from notepadnext.

which should be paid around $99/year

Knowing Apple this doesn't surprise me. 😡

Not something I'm willing to invest in for a while. So sounds like homebrew won't be supported for the foreseeable future.

from notepadnext.

I can submit the package to the homebrew but the .dmg file should be signed first.

macOS on ARM requires software to be signed.
Please contact the upstream developer to let them know they should sign and notarize their software.

This is the error message I'v got when I try to do that.

from notepadnext.

I added the temporary PR #531 where it uses this repo as the custom tap. When you sign the package correctly, then I can add the package to the main homebrew-cask later.

from notepadnext.

How do I sign the package?

from notepadnext.

I don't know either but AFAIK you require the apple developer id and some process. If the package is not signed, then the only way to serve the package through the brew is the custom tap and cannot submit to the homebrew-cask.

from notepadnext.

I don't know either but AFAIK you require the apple developer id and some process.

I've not had anyone actually describe the process or tell me what is needed. I don't know this process at all and don't want to have to add yet more work into a release process. If it can be automated, I'd definitely consider it.

Even if the package is not signed do you still see #531 as being valuable?

from notepadnext.

Yeap, just one more command line to tap your repo. Without automation, someone have to update the version info manually but also it can be done easily with brew command.

brew bump --cask --open-pr notepadnext

All this is for use of cli not manually install the package and so it will be valuable.

from notepadnext.

I read several articles how to sign for the package, for example:

• https://blog.pakkly.com/how-to-sign-qt-apps-on-mac-for-release/

It requires the apple developer id which should be paid around $99/year and so maybe the third-party tap is reasonable if you are not plan to support macOS extensively.

from notepadnext.