A Comprehensive Guide to Linking Specific Versions in Homebrew

In macOS systems, Homebrew is a widely used package manager that allows users to install and manage various software packages. However, when multiple versions of the same package exist, linking to a specific version becomes a common technical challenge. This article systematically addresses this issue based on high-scoring answers from Stack Overflow.

Installing Specific Versions with @ Symbol

Since Homebrew version 2.6.0, the recommended method is to use the @ symbol to directly install specific versions. For example, to install PostgreSQL 9.5, simply execute:

$ brew install postgresql@9.5

This approach is concise and efficient, directly specifying the target version and avoiding subsequent linking operations. Homebrew automatically handles dependencies and symbolic links, ensuring the system uses the correct version.

Listing Available Versions

Before installation, users may need to know which versions are available for a package. This can be done by searching with the @ symbol appended to the package name:

$ brew search postgresql@

After executing this command, Homebrew lists all available PostgreSQL versions, including stable and development releases. The output typically includes Formula (for command-line tools) and Cask (for graphical applications) sections.

Deprecated brew switch Command

Prior to Homebrew 2.6.0 (released in December 2020), users could switch between versions using the brew switch command. Its basic syntax is:

brew switch <formula> <version>

For example, to switch MySQL to version 5.5.29, execute:

brew switch mysql 5.5.29

To view installed versions, use the brew info command:

brew info mysql

If attempting to switch to a non-existent version, Homebrew displays available version numbers. For instance:

brew switch mysql 0

Although brew switch is deprecated, understanding its functionality helps address legacy issues in older systems or specific scenarios.

Historical Methods: brew versions and homebrew/versions Repository

In earlier Homebrew versions, the brew versions command listed all available versions of a package. This command has been removed, but if still needed, first run:

$ brew tap homebrew/boneyard

Another historical method involved installing older versions via the homebrew/versions repository:

$ brew tap homebrew/versions
$ brew install mysql55

This approach managed older packages through a dedicated version repository, but over time, Homebrew has standardized on the @ symbol method.

Practical Case Analysis

Suppose a user has multiple versions in the /usr/local/Cellar/libfoo directory: 1.0.1, HEAD, and mycopy. To link to version 1.0.1, first ensure it is installed. If not, use:

$ brew install libfoo@1.0.1

After installation, Homebrew automatically creates symbolic links. For manual management, inspect versions in /usr/local/Cellar/libfoo and use system tools like ln, but relying on Homebrew's automation is recommended.

Best Practices for Version Management

In multi-version environments, follow these best practices:

1. Prioritize installing specific versions with @ symbols for precise version control.
2. Regularly use brew update and brew upgrade to keep Homebrew and packages updated, but note this may affect version stability.
3. For production environments, consider using virtual environments or container technologies to isolate different versions and avoid system-level conflicts.
4. Consult official documentation and community resources for the latest changes, as Homebrew's version management strategies may evolve.

Through these methods, users can flexibly manage software package versions in Homebrew, meeting diverse needs in development, testing, and production.