brightintosh: deprecate

[niklasr22]

Removes the brightintosh cask because I can no longer provide the prebuilt application at this time.

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.
• Checked the cask is submitted to the correct repo.
• 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 think the cask can be disabled but not simply deleted.

install: 100 (30 days), 229 (90 days), 334 (365 days)

[bevanjkay]

@niklasr22 Can you please explain the situation a bit more? I can see that the latest version is still available from - https://c.brightintosh.de/updates/BrightIntosh_v1.6.1.dmg
If development has ceased since this release, we would be better to use deprecate with a reason of :discontinued.

[niklasr22]

@bevanjkay Development is still active. For now I want to only distribute the built application through Apples App Store as donations didn't cover the costs of providing notarized builds.

[bevanjkay]

@niklasr22 No worries, thanks for the update. We should still use the deprecate stanza, but the reason can be :moved_to_mas so that users are pointed in the appropriate direction.

[chenrui333]

we dont do straight removal at best, I will update this PR to use :moved_to_mas like @bevanjkay said.

[niklasr22]

Thank you @chenrui333! Sorry I couldn't find time yet.