tigerbrew: a Homebrew fork for PowerPC Macs and Mac OS X Tiger

A fork that exists because the hardware stopped being supported

Homebrew stopped supporting PowerPC Macs and Mac OS X Tiger long ago, and Tigerbrew exists to fill that gap. The README describes it as a little experimental fork of Homebrew that adds support for PowerPC Macs, and Macs running Tiger or Leopard.

The project is a fork in the literal sense. The repository is a Ruby codebase with the standard Homebrew shape: a Library/ directory holding the formulae, bin/ for the command line entry points, share/ for the man pages and completions, plus .yardopts, CONTRIBUTING.md, CODE_OF_CONDUCT.md and SUPPORTERS.md. The credits name Homebrew as originally written by mxcl, and state that the fork is by mistydemeo and incorporates some code originally written by @sceaga.

The licence is BSD 2 Clause, the NetBSD variant, with the text in LICENSE.txt. That is a permissive licence with no copyleft obligation, so a company can run the fork internally without the licensing question that a copyleft dependency would raise.

The audience is narrow and clear: people with a PowerPC iMac, a PowerPC Mac mini or PowerBook, or a machine that is stuck on Tiger or Leopard, who want to install command line packages without hand-compiling them. The word experimental in the README is doing real work there, and it comes back later in the FAQ.

The repository is not archived and the last push was on 2026-10-10, so the fork is still being worked on even though there are no GitHub releases to mark versions.

The installer is a script you drag into a terminal

The installation flow is unusual, and it is unusual for a good reason: you probably cannot reach the machine you are installing on the way you normally would.

The first prerequisite is Xcode, and it has to be the newest version for your operating system. The README names Xcode 2.5 for Tiger and Xcode 3.1.4 for Leopard, with links to Apple's download pages, and it states that both downloads require an Apple Developer account. That is the first hard constraint: the oldest supported system here needs a developer credential to obtain its compiler.

The second step is to fetch the installer. The README asks you to save the linked file to disk from the computer you are reading the page on, giving this raw address:

<https://raw.github.com/mistydemeo/tigerbrew/go/install>

Then you transfer that file, along with Xcode, to the Tiger or Leopard machine. The README notes that advanced users may prefer to use TenFourFox instead, which is a reasonable suggestion if the browser on that machine is the thing that will not cooperate.

The final step avoids typing a long path. You type ruby followed by a space in the terminal, then drag and drop the install file onto the terminal window so the path is inserted for you, and press return. The install script therefore runs under the system Ruby that ships with those versions of Mac OS X, which is also why the instruction is to type ruby explicitly rather than run the file directly.

The whole procedure assumes you are moving files between machines by hand, which is the situation this fork is built for.

PATH has to be fixed by hand on these systems

One detail in the README is worth isolating, because it is the kind of thing that produces a confusing first failure.

The installer does not set up your shell path for you. On later versions of Mac OS X, /usr/local/bin is already in the default PATH. On Tiger it is not, so the README tells you to make sure that /usr/local/bin and /usr/local/sbin are in your PATH, and gives the exact line to add to your ~/.bash_profile if you use bash:

export PATH=/usr/local/sbin:/usr/local/bin:$PATH

The order matters in the sense that the Homebrew directories come before the rest, which is the convention Homebrew itself uses so that its programs win over any system copy of the same name.

Two practical notes. First, this only covers bash. The README mentions ~/.bash_profile, and says nothing about zsh or csh configuration, so on a shell other than bash you have to translate the line yourself. Second, a shell that has never been set up this way will find brew and its installed programs only after that line is in place, which means an installer that appears to have run successfully but whose brew command is not found is the expected first symptom rather than a broken install.

Once the path is right, the commands the README points you to are the familiar ones. You can browse the Formula directory on GitHub, type brew search for a list, or use brew desc to browse packages from the command line. brew help, man brew and the project wiki cover the rest.

Converting an existing Homebrew install with git

Most people who want Tigerbrew already have Homebrew installed, so the FAQ answers the migration question directly. The instruction is to run four commands from the terminal, and it requires git to be installed.

cd `brew --repository`
git remote set-url origin https://github.com/mistydemeo/tigerbrew.git
git fetch origin
git reset --hard origin/master

The mechanism is worth understanding rather than just copying. Homebrew manages itself as a git checkout of its own repository, so switching to the fork is a matter of pointing the origin remote at the fork, fetching it, and hard-resetting your working copy onto the fork's master branch. The hard reset discards local modifications, which is the right behaviour for a package manager whose formulae you should not be editing by hand.

The next FAQ entry covers a specific failure mode of that setup. If brew update fails when your installation lives in /usr/local, the README tells you to run:

git config --global --add safe.directory /usr/local

That is git's ownership check on a directory. When the repository directory is owned by a different user than the one running git, recent git versions refuse to operate on it, and the safe.directory setting is the documented way to declare the directory trusted. It is worth knowing why the command exists, because a global git configuration change is the kind of thing a security reviewer will ask about, and adding a path you own to the safe list is the intended use.

One caveat the README does not spell out: this migration replaces your Homebrew checkout wholesale, so any local changes or extra formulae you added are gone after the reset.

The honest part: many formulae are untested

The FAQ ends with a section titled Something broke, and it is the most useful paragraph in the README.

The text says that many of the formulae in the repository have been tested, but that there are still many that have not been tested on Tiger and/or PowerPC yet. If something does not work, you are asked to report a bug or submit a pull request.

That is an accurate description of a fork's actual state, and it is the thing to weigh before you rely on it. The formulae that work are the ones somebody happened to test on that particular machine. A formula that fails on a 2006 PowerPC Mac may fail for a reason that has nothing to do with Tigerbrew's changes, such as a source tarball that has moved, a compiler flag that no longer applies, or a dependency that never had a PowerPC build.

There are no GitHub releases to track versions, so there is no changelog telling you which formulae changed between two points in time, and the last push was on 2026-10-10 with the commits landing directly on master.

The practical consequence is that a Tigerbrew installation is a working environment for the packages that have been checked and a research project for the ones that have not. Installing a few dozen formulae and finding which ones break is a reasonable first afternoon, and it is the way the project itself expects to learn which formulae need fixing.

Editorial conclusion

tigerbrew fits an owner of a PowerPC Mac or a Tiger or Leopard machine who wants a familiar command line package manager on hardware Apple no longer supports, and who can supply an Apple Developer account and the matching Xcode for the machine. It is the wrong choice for a modern Mac, where upstream Homebrew is the maintained path, and it is the wrong choice for anyone who needs a formula that has never been tested on that architecture, since the README says many formulae remain untested on Tiger and PowerPC. Before installing, check that you can still obtain Xcode 2.5 or 3.1.4 for your system, set the PATH line the README requires, and expect to fix individual formulae yourself.

Frequently asked questions

Official sources

1. Issues
2. License: BSD-2-Clause
3. mistydemeo/tigerbrew on GitHub
4. README