Sudo-based Cask Installation vs. User-Level Application Paths

Privilege Escalation in Cask Management

Homebrew typically invokes sudo to install casks into system-wide locations such as /Applications. This process relies on the system's sudoers configuration, meaning users are prompted for credentials whenever the sudo timestamp expires during a long installation or across multiple batch installs.

Least-Privilege Trade-offs

While the current model ensures that only necessary operations are elevated, it creates a dependency on the system's authentication timeout. There is a design tension between maintaining strict least-privilege access and providing a seamless installation experience that avoids repeated password prompts.

An alternative approach would be to support user-level installation paths for casks, effectively removing the need for sudo by writing to directories owned by the current user.

• Sudo-based: Maintains standard macOS application placement but risks installation failure if the user is unavailable to refresh expired credentials.
• User-level: Eliminates privilege escalation requirements but deviates from standard system application paths.

Which approach better aligns with Homebrew's philosophy for cask management? Should Homebrew introduce a configuration to redirect casks to a user-owned directory to bypass sudo entirely?