Publish MacOS package to homebrew

[vdsirotkin]

Hey! Homebrew (https://brew.sh/) is a very popular package manager for MacOS. It would be nice if you publish updates there :)

Thanks!

[dail8859]

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).

[daeho-ro]

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.

[daeho-ro]

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.

[dail8859]

How do I sign the package?

[daeho-ro]

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.

[dail8859]

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?

[daeho-ro]

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.

[daeho-ro]

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.

[dail8859]

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.

[popey]

Sorry to necro a closed issue. I just downloaded NotePad Next on my MacOS machine and got the usual nonsense from Apple about it being insecure. In case you weren't aware, this is what it looks like:

Users then have to choose to eject the disk image and forget the app, or navigate to a scary place...

Click 'Open Anyway'. Type in their password, or press the fingerprint button, then more scary text:

Finally:

I just wanted to mention quill which is a tool my employer made, which enables you to sign Mac binaries without having a Mac, and automagically. We use it to sign our MacOS binaries of other software we make.

This does still mean you have to pay the Apple Tax of $99/year.

I really value the work you have done on NotepadNext, so would volunteer to pay your first two years of $198 (around £155 in my local currency), as a gift, if that helps you. No worries if not, I won't be offended.

Making a signed binary is more work for you, of course, but it means potentially more users. You may even want to publish it in the Apple MacOS store at some point, and you could very easily charge for that. As you probably know, MacOS users tend to have credit cards on file, so purchasing flow is smoother than on other platforms.

But that introduces even more admin for you. Which I completely respect, if you'd rather not have to deal with. 🙏

Thanks and again, apologies for ressurecting a closed issue.

[dail8859]

In case you weren't aware, this is what it looks like

That's definitely good to see!

I really value the work you have done on NotepadNext, so would volunteer to pay your first two years of $198 (around £155 in my local currency), as a gift, if that helps you.

That is quite the gracious offer! But for now I don't feel the extra work involved in signing it is worth it. I have no way to test/support/debug anything Mac related so it has been only made available by other willing to offer their support.