1
edit
Changes
→Install and update fink: Upgrade from PPC to Intel fink is not possible. Full delete and fresh install is necessary.
<ol><li> Download the appropriate version of [http://fink.sourceforge.net/download/index.php?phpLang=en fink]. These instructions were tried with fink 0.8.1. You may need the [http://fink.sourceforge.net/doc/users-guide/ Fink User's Guide].
<li> Install fink by opening the disk image and double clicking on the installer.pkg.
<ul><li>Update note for Mac OS X 10.5 on an Intel Mac where fink had been copied across from your old PPC (ie. G4 or G3) Mac. You have to delete your entire PPC-based fink and install freshly the fink 0.9. Upgrading first wastes your downloads and time, as the PPC version will not upgrade to the Intel version.</li></ul>
<li> You could use FinkCommander to provide a GUI to fink, but it is not worth the trouble, because I wasn't sure that it actually offered all the packages that I wanted, and sometimes did not allow me to type in responses to questions (this is presumably a bug). I suggest you use Terminal. In Terminal type <tt>'''fink selfupdate'''</tt> This should download package descriptions and update core packages including fink itself. I thought it would be best to do this update before switching from source to binary distribution, but I had to try the whole updating process several times before I actually managed to get it to succeed, so this may be a bad choice.
<li> In Terminal type <tt>'''fink configure'''</tt> This should run the fink configuration process (or it may have been run automatically before). You need to choose source distribution (not binary). This will set the list of Trees in <tt>'''/sw/etc/fink.conf'''</tt> to have unstable/main at the end. If not you need to add this manually. Because <tt>fink.conf</tt> is owned by root, if you do this manually you will have to do <tt>'''sudo pico /sw/etc/fink.conf'''</tt>. During the configuration process you will also have to choose between the CVS (Concurrent Versions System or Concurrent Versioning System) and rsync update methods. Rsync is a very fast protocol. It will update the description files faster than the old CVS update method. Furthermore, CVS updates are always done from sourceforge.net while rsync updates can be done from a mirror close to you. I found that CVS often stalled trying to access files, though rsync had the disadvantage that sometimes files were not found (and perhaps as CVS uses the master copy the files should be found). Nevertheless, I suggest you use rsync. If you are behind a firewall (even the firewall in a broadband router), you may need to set ProxyPassiveFTP to true to help get around the firewall.
