Fink

Installation - 2 First Time Installation

2.1 Requirements

You need:

2.2 Choosing A Directory

Before you install, you must decide where Fink's directory hierarchy will live. The recommended place is /sw, and all examples in this document will use that. Any other directory should be fine as well, as long as you don't use existing directories like /usr/local or /usr. The bootstrap script tries to catch these.

If you intend to use the binary distribution (through apt-get / dselect), you must install to /sw. Unfortunately, binary packages are not relocatable.

The directory that you choose must not contain any spaces or similar. Both Unix itself and the bulk of Unix software were written under this assumption. Using symlinks to trick the bootstrap script simply won't work.

A special note about /usr/local: While it is possible to install Fink in /usr/local (and the bootstrap script will let you do that after a confirmation), it is a bad idea. Many third party software packages install into /usr/local. This can cause severe problems for Fink, including overwriting files, dpkg refusing to install packages and strange build errors. Also, the /usr/local hierarchy is in the default search path for the shell and the compiler. That means that it is much more difficult to get back to a working system when things break. You have been warned.

2.3 Installation

First, you need to unpack the fink-0.9.0-full.tar.gz tarball. (Note: If you have OS X 10.4 and XCode 2.1, you should use fink-0.8.0-full-XCode-2.1.tar.gz instead, and make the appropriate changes below.) It is recommended that you do this from the command line - StuffIt Expander has a tendency to screw up text files. So, go to the directory where you put the tarball, and run this command:

tar xzf fink-0.9.0-full.tar.gz

You now have a directory named fink-0.9.0-full. Change to it with cd fink-0.9.0-full.

The actual installation is performed by the perl script bootstrap. So, to start installation, go to the fink-0.9.0-full directory and run this command:

./bootstrap

After running some tests, the script will ask you what method should be used to gain root privileges. The most useful choice is 'sudo'. On a default install of Mac OS X, sudo is already enabled for the user account created during installation. The script will immediately use the method you choose to become root. This is required for the installation.

Next, the script will ask you for the installation path. See 'Choosing A Directory' above for hints about this. The script will create the directory and set it up for the bootstrap that will be done later.

Next up is Fink configuration. This consists mainly of setting proxies and selecting mirror sites for downloading. The process should be self-explaining. If you don't know what to say, you can just press Return and Fink will use a reasonable default value.

Finally, the script has enough information to conduct the bootstrap process. That means it will now download, build and install some essential packages. Don't worry if you see some packages being compiled twice. This is required because to build a binary package of the package manager, you first must have the package manager available.

2.4 Getting X11 Sorted Out

Fink uses virtual packages to declare dependencies on X11. As there are several X11 implementations available for Mac OS X (XFree86, Tenon Xtools, eXodus) and several ways to install them (manually or via Fink), there are several actual packages - one for each setup. Fink is quite bad at guessing what you have, so it's best to get this sorted out right at the beginning. Here is a list of the available packages and installation methods:

For more information on installing and running X11, refer to the online X11 on Darwin and Mac OS X document.

Next: 3 Upgrading From Fink 0.3.x