Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

BetterMouse and uhk-agent not marked as auto_updates #197357

Closed
3 of 6 tasks
Bendodroid opened this issue Jan 6, 2025 · 2 comments · Fixed by #197497
Closed
3 of 6 tasks

BetterMouse and uhk-agent not marked as auto_updates #197357

Bendodroid opened this issue Jan 6, 2025 · 2 comments · Fixed by #197497

Comments

@Bendodroid
Copy link

Verification

Description of issue

The BetterMouse cask is not marked as auto_updates so having brew update the cask after the internal updater has already updated the application leads to slightly weird behavior (and an unnecessary download etc.).
Happened to me in the past (not recently), but only had the spoons to check why right now.
The same applies to uhk-agent which also has an internal updater.

BetterDisplay on the other hand has an internal updater and is marked as auto_updates.

So what's the reasoning here why the other two are not left alone by brew? Or did someone just forget to add the tag at some point? I skimmed through the git history for the cask files but didn't find any answers.

Command that failed

n/a

Output of command with --verbose --debug

n/a

Output of brew doctor and brew config

n/a

Output of brew tap

n/a
@khipp
Copy link
Member

khipp commented Jan 6, 2025

Or did someone just forget to add the tag at some point?

That's very likely. Applications may also add or remove update functionalities at some point.

Feel free to open a PR to add auto_updates true to those casks!

@Bendodroid
Copy link
Author

Oh wow, that was quick :D Thanks to both of you @yunhao-jiang

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants