bundle: write to tab through the wrapper

[Bo98]

Some external brew wrappers treat brew bundle with lower permissions due to its execution of user code. In such scenarios, writing to the Homebrew prefix might fail. Running through brew tab will avoid these issues as it will go through the brew wrapper again, and more closely mimic how the rest of brew bundle works (e.g. issuing brew install commands).

This will be a little slower but will generally only be a one-time operation anyway.

[Copilot]

Pull request overview

This pull request changes the mark_as_installed_on_request! method to use brew tab --installed-on-request command instead of directly writing to tab files. This approach ensures proper privilege escalation when using external brew wrappers that restrict brew bundle permissions due to user code execution.

Changes:

• Refactored from individual tab file writes to a batched brew tab command invocation
• Changed from .each iteration with immediate writes to .filter_map collecting formula names for batch processing
• Added explanatory comment about wrapper privilege handling

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[MikeMcQuaid]

Could this instead go through the wrapper only if the write fails given it's a slowdown?

[Bo98]

Sure, I think Errno::EACCES is enough. Or at least it is for my case.

[MikeMcQuaid]

Thanks!