DomT4/homebrew-autoupdate

Add terminal-notifier as a recommended/optional depency

TheHarcker opened this issue · 4 comments

It would be nice if terminal-notifier would be listed as a (required/optional/recommended) dependency for brew to install along with autoupdate.

Will the above be impossible due to this only being a tap and not a full fledged formula?

If it is impossible, it would be nice to have a simple brew install terminal-notifier in the README.md

DomT4 commented

It would be nice if terminal-notifier would be listed as a (required/optional/recommended) dependency for brew to install along with autoupdate.

I've put a fair bit of thought into this over time. My thoughts have generally pooled into:

  • Would it be possible to rewrite the notification output to use system notifications without needing an external dependency to achieve this, without increasing the maintenance this project requires significantly?
  • Would it be prudent to ship my own bundled terminal-notifier.
  • If yes, how to achieve this without asking users to simply straight up trust me putting a binary blob on their system without doing anything nefarious. I never would and I know a chunk of people trust me because I used to be a core maintainer over at Homebrew before I left the project, but I also completely understand and empathise with people being wary of random people vendoring external dependencies.

Would it be possible to rewrite the notification output to use system notifications without needing an external dependency to achieve this, without increasing the maintenance this project requires significantly?

@DomT4 Hi, the part you wrote above sparked my interest.

It seems to be possible to create a system notification from an AppleScript script. If we are able to run an AppleScript and get the clients system to trust this script, this might be doable.

Let me know what you think!

Source

DomT4 commented

6365cc0, f31a161, 8b12c22, e2b76a0, 6a084e3, 6bc10b3, 322bb03 together implements a new, experimental notification system that uses Applescript to execute and doesn't rely on or need any external dependencies. At the moment it only runs on macOS Big Sur, which is largely my way of testing it in a limited roll-out before turning it on for everyone. The applet is also codesigned, so should run on other macOS machines.

As with most brew-autoupdate changes to cause minimal disruption I haven't automatically pushed the change through to users locally; if you wanted to change to the new notification system on Big Sur you'd need to manually brew autoupdate --delete and then brew autoupdate --start again.

DomT4 commented

Folded into #43.