Reconsider default installation path

[tapeinosyne]

I would like to propose /Applications as the default installation path, changing from the current ~/Applications. For past opinions surrounding this issue, see #30.

To better direct the discussion, note that I am not arguing that installing to /Applications is strictly better practice than installing to ~/Applications. My suggestion is that symlinking apps to /Applications would be a better default, as it is where most users expect to find their apps based on common practice. Consider the following:

• As of 10.7, OSX does not create ~/Applications. A user application folder is supported, but optional. On 10.6, the user application folder was created empty. See thread on Apple Support.
• The Mac App Store installs to /Applications. I would expect most Cask users to have at least one MAS-only application they like or need (cue harrowing screams of those who like to automate provisioning of their machines), which is problematic for those who favor ~/Applications as some of their software will be relegated to the global folder.
• Homebrew changed the default --linkapps path to /Applications about five months ago with Change brew linkapps to use the global /Applications folder legacy-homebrew#22378. (--linkapps symlinks certain programs, e.g. Emacs, to a folder, similarly to Cask.) Given that Cask is implemented as an external brew command, it should be desirable to mantain consistent behavior for shared functionality.
• Other applications seemingly expect the absence of a user application folder. E.g. Alfred, a very popular tool, does not include ~/Applications in its search scope.

I find these to be increasingly good reasons to adapt our current default path; the trend appears rather clear. Of course, Cask would remain configurable, and those who prefer to keep Cask application separate will be able to change their installation folder with export HOMEBREW_CASK_OPTS. However, most users (particularly new ones) would be better served by the more common /Applications as default.

[adamv]

I was -1 on the Homebrew change here, and prefer ~/Applications, but didn't fight it. FWIW.

[muescha]

+1 for change, because if the parent take this change, then the users expect the same change also here.

[vitorgalvao]

Alfred, a very popular tool, does not include ~/Applications in its search scope.

It also does not follow the created links, so even if apps were symlinked to /Applications, it would make no difference to it.

That said, I agree the default should be /Applications, it’s way more intuitive.

[tapeinosyne]

@vitorgalvao Perhaps I was unclear: my meaning was that Alfred also considers the ~/Applications folder passé, unrelatedly to Cask.

[goxberry]

I'm -0.1 on this change. I think /Applications is much more intuitive, and certain casks containing packages (here, I'm thinking specifically of MacTeX; there could be others) install to /Applications already.

At the same time, I like having cask-installed apps in a separate location. It also makes having multiple copies of apps intuitive. For instance, my employer manages some software in /Applications, and they can be stubborn about versioning and patching, so it is helpful in that situation to install my preferred versions in a separate location.

[rolandwalker]

• I personally use homebrew-cask to install to /Applications, but am fine with the default
• Alternate usecases could be better accommodated by adding a prefs file caskrc (instead of, or in addition to, environment variables, which are a bit fragile). I would advocate for, and assist with, such a patch.
• This particular question is not just an either/or switch, right? Every author writing backend code did so under the assumption that it normally did not run under sudo. Someone would have to do the work of auditing the code and submit patches for best practices when running as a privileged user.

[majjoha]

I am definitely +1 on changing the default folder to /Applications as well. It was where I expected my applications to be placed, and I'd assume that most people would look for them in that folder too.

[StevenClontz]

Homebrew changed the default --linkapps path to /Applications about five months ago with Homebrew/legacy-homebrew#22378. (--linkapps symlinks certain programs, e.g. Emacs, to a folder, similarly to Cask.) Given that Cask is implemented as an external brew command, it should be desirable to mantain consistent behavior for shared functionality.

This is the big issue for me. In addition, certain casks which rely on installers are installed to /Applications anyway (see: Vagrant and Virtualbox).

[lgarron]

This is the big issue for me. In addition, certain casks which rely on installers are installed to /Applications anyway (see: Vagrant and Virtualbox).

The same applies to me. I don't really care if my applications are in /Applications or ~/Applications, but I believe I've observed the following:

• Things breaking because certain applications are expected to be in /Applications.
• Applications breaking because they are symlinked instead of hard-linked/copied.

For this reason, I always install to /Applications and replace the symlink with a copy (the last step is manual). I don't know if this is necessary, but I had enough initial issues with brew cask installations that I prefer this hassle to unexpected breakage later on.

[keith]

As the creator of that original PR mentioned I definitely still +1 this.

[hanxue]

+1 for homebrew cask to symlink to /Applications

[AlJohri]

+1 for homebrew cask to symlink to /Applications

Also +1 to

+1 for change, because if the parent take this change, then the users expect the same change also here.

For now, I have to do this on every computer I use homebrew cask with:

export HOMEBREW_CASK_OPTS="--appdir=/Applications"

[alebcay]

On the other hand, if we did implement such a change, we'll receive the following complaint:

For now, I have to do this on every computer I use homebrew cask with:

export HOMEBREW_CASK_OPTS="--appdir=~/Applications"

[dmyers]

👍 ➡️ /Applications