Cask au-lab add proper permissions to make the app function with audio input

[mmoole]

Output of brew config

HOMEBREW_VERSION: 4.4.15
ORIGIN: https://github.com/Homebrew/brew
HEAD: b6fafba4864d65acabf966415e14b2dd86d81e1a
Last commit: 7 days ago
Branch: stable
Core tap JSON: 11 Jan 17:58 UTC
Core cask tap JSON: 12 Jan 11:28 UTC
HOMEBREW_PREFIX: /opt/homebrew
HOMEBREW_CASK_OPTS: []
HOMEBREW_MAKE_JOBS: 12
Homebrew Ruby: 3.3.6 => /opt/homebrew/Library/Homebrew/vendor/portable-ruby/3.3.6/bin/ruby
CPU: dodeca-core 64-bit arm_brava
Clang: 16.0.0 build 1600
Git: 2.47.1 => /opt/homebrew/bin/git
Curl: 8.7.1 => /usr/bin/curl
macOS: 15.2-arm64
CLT: 16.2.0.0.1.1733547573
Xcode: N/A
Rosetta 2: false

Output of brew doctor

Please note that these warnings are just used to help the Homebrew maintainers
with debugging if you file an issue. If everything you use Homebrew for is
working fine: please don't worry or file an issue; just ignore this. Thanks!

Warning: Some installed casks are deprecated or disabled.
You should find replacements for the following casks:
  speedcrunch

Description of issue

When using the current au-lab cask, one gets a working Au Lab app, but it isn't able to get sound via input since it doesn't ask for microphone permissions.
On ExistentialAudio/BlackHole#4 (comment) a solution for this is mentioned:

• codesign the app with an appropriate .plist which makes the app then, at the next run, ask for microphone permission.

I tried this on MacOS 15.2 and it works.

I hope this could be added to the cask as it almost looks like only one or two lines of code.
This would then allow us to use the app straight after having the cask installed.

Relevant casks

au-lab

[daeho-ro]

I think this should be done by upstream?

[SMillerDev]

It applies to all installs of it. Homebrew shouldn't be the one to ask, the users should be.

[mmoole]

Then maybe homebrew could display a hint about how to do it right after installing?
I remember it displaying a hint for caveats after installing some other apps, but don't remember the exact apps precisely...Maybe cask perforce could be an example for that.

[daeho-ro]

The caveats can be used when the issue is related to HomeBrew not for general. The issue is clearly comes from the upstream and here is not the place to fix it. But you may use your custom tap to fix by your own cask, whatever you can do with it.

• https://docs.brew.sh/How-to-Create-and-Maintain-a-Tap

[mmoole]

So is there a proposed way to inform users about this problem when installing the cask, or does homebrew keep this knowledge here? (I assume upstream won't care about that this year)

[SMillerDev]

There isn't really anything the users or Homebrew can do about this. It's really up to upstream to fix their software, so they should be notified.