Here is what I did to build and install Alpine on my Mac OS X system.
- If you have not done so already, download and install the latest Xcode package from the Apple Developer Center.
- Backup any Pine and Alpine files that are in
/usr/local/bin. These will be replaced by Step 13 below.
- Go to ftp.cac.washington.edu/alpine and get the latest alpine-x.xx.tar.bz2 (where x.xx is the version number). I prefer to get the .bz2 file because it is smaller than the .Z and .gz files.
- Put this tarball in your build directory, for example in ~/Build.
- Open a Terminal window.
- To change to your build directory, type:
- To check the MD5 checksum of the tarball, run one of the following commands:
/sbin/md5 /absolute/path/to/alpine-x.xx.tar.bz2 /usr/bin/openssl md5 /absolute/path/to/alpine-x.xx.tar.bz2I recommend that you specify the absolute path to both the command and the tarball to ensure you are not specifying trojans. The MD5 checksum should match the MD5 checksum that is in the x.xx release announcement message.
- To list the table of contents of the tarball, type:
tar jtvf alpine-x.xx.tar.bz2 | lessNote:
j = bunzip2 t = table of contents v = verbose f = file
- To unbzip2 (bunzip2) and untar the tarball, type:
tar jxvf alpine-x.xx.tar.bz2Note:
j = bunzip2 x = extract v = verbose f = file
- To change to the newly created alpine-x.xx directory, type:
- To read the README and the configuration help, type:
less README ./configure --help |less
- To build Alpine, type the following (which are discussed in the README):
- After the build is finished, type:
sudo make installYou will be prompted for your Mac OS X password. Note that you need to be using an OS X admin account to use sudo and that this command will replace any Alpine files that are in
- To check that Alpine was built and installed correctly, type:
man alpine alpineMake sure that these two commands invoke the correct version (x.xx). If these commands do not work, you probably need to add /usr/local/man to your MANPATH environment variable and /usr/local/bin to your PATH environment variable. For details, see the man page for your shell (man bash, man tcsh, etc.). To determine your shell, run finger -l.
- man alpine
- alpine -h | less
- Alpine Release Notes, which can be viewed either here or by typing MR (Main > RelNotes) in Alpine
- Alpine's built-in context-sensitive Help, which can be viewed by typing either ^G (Get Help) or ? in Alpine
- Alpine-alpha list archives
- All About Pine: POP, IMAP, NNTP, & ESMPT Client for Unix, MS Windows, and Mac OS X
- Power Pine: Getting the Most Out of Unix-, Mac-, and PC-Pine
Tip 1: You should be able to use a modified version of these instructions to build Alpine on any Unix-like system. For example, I used Steps 3-12 to build Alpine on my DreamHost shared hosting account, which runs Debian Linux.
Tip 2: The Alpine FTP site includes pre-built versions of Alpine for MS Windows (PC-Alpine): alpine-x.xx-wnt.zip and setup_alpine_x.xx.exe. Details are in ftp://ftp.cac.washington.edu/alpine/README
- Paul Heinlein's madboa.com: Pine and Alpine on Mac OS X, which includes notes on building and running Pine or Alpine under Mac OS X.
- University of Washington: Alpine Technical Notes: Building and Installation
Hashtag: #building-and [?]
Post & Read Comments (located elsewhere)
Post & Read Comments (located here)
Speaking of which, I followed those, and the .mbox files procmail made aren't being read by Thunderbird or Mail. I'm so tired of diligently trying to do this and coming up against errors like this and then not being able to find anyone else experiencing the same problems no matter how hard I look.
Links to this page
Each item © Nancy McGough
Each comment © the author of the comment
Deflexion.com web site hosted by DreamHost.com
← More deflexions & reflexions, & feeds available via the sidebar top &
For bookmarks & links, please use