![]() configure make make install ten thousand times and giving up your system to the whims of a bunch of unknown package maintainers. I think it's a good compromise between typing. MacPorts is a source-based distribution mechanism much like FreeBSD's ports, so it offers you the chance to just let it handle everything for you if you really don't care which compiler flags you pass to the cowsay utility, but do want more fine-grained control over what goes into apache, mysql, etc. My MacPorts repository of software is also more compact for some reason it's about half the disk space of the similarly-equipped fink tree I used to maintain. Fink packages would often just simply not install, or have versioning/testing issues that I had to go in and fix myself from the source. I found (subjectively) that the packages in MacPorts were kept more up to date, and had fewer tendencies on install to get into mutual-dependency loops of death. One day, I tried out MacPorts, and never switched back to fink. As of fink 0.29.9, the mirror configuration is the last thing that you are offered for reconfiguration.I used Fink for quite a while. This reconfigures all of fink, but you can just step through the questions and accept the default answers to leave the current settings unchanged. To change the current mirror configuration, with hope for better luck, issue this command ![]() In some cases I had to manually download certain files and dump them in /sw/src. In my experience fink mirrors are unreliable, in fact one of the major issues I have with fink is that simply downloading the required packages often does not work unsupervised. Packages whose builds had succeeded before the crash will not need to be rebuilt.įor details see (the page that the above quote was taken from, accessed January 11 2009). Note that for complex build requests, you may have to go through several iterations of build-a-package/retry-the-whole-set.each time you will get further through the process. The crash will tell you which package fink was trying to build at that moment: try to have fink build just that package, which will usually succeed, then you can retry the original command that led to the crash. In my experience, virtual machines are much more stable than Wine for running Windows applications. Also consider running Windows in a VM such as VirtualBox, VMware Fusion, or Parallels. Sometimes if you request a build that entails many other builds or have a single fink command build many packages at once (for example, fink update-all), it will try to build a package with the wrong dependencies installed. MacPorts or Fink might be overkill just to run Wine. The dependency engine used by fink is not perfect. If the system-wide xinitrc alredy exists, a backup is made. If you don't know what all of this is about, just say yes. Alternatively, you canĪlso bypass our standard mechanism by creating following file. Note that you can achieve many of what you want If you customized it and don't want it to be replaced, say no here and In the process of installation, Fink said the following:įink X11 startup framework needs to replace following file: I recently installed Fink from scratch (package manager version 0.28.6, distribution version 0.9.0/selfupdate-rsync) and the first thing I installed was the package digikam. Trees: local/main stable/main stable/crypto unstable/main unstable/cryptoĪfter enabling the unstable tree, you must still download the package descriptions: If the question does not appear, manually edit /sw/etc/nf so that the "Trees" line looks like something like this: To switch from stable to the unstable distribution, runĪnd answer the question about turning on unstable with "yes". I usually install XQuartz because I want to run the latest version of The Gimp, which usually requires a newer version of X11 than the one provided by Apple. If you have no compelling reason to do otherwise, you should use Apple's version because it is the official thing. Either install the version provided by Apple, or use something newer from the XQuartz project. ![]() I personally prefer to have the following software installed on a system before I start with Fink: The easiest way to install a basic Fink environment is to download the installer disk image from and follow the quickstart guidelines on the same page. usr/local/fink), however /sw is canonical and a lot of documentation and sometimes even software rely on this location. In theory it is possible to choose a different directory (e.g. ![]() The major point here is that Fink installs all its files in a special location on the file system, the folder FAQ (I mostly use this document when I don't remember how to install or update fink)įink tries to keep out of the way of Mac OS X as much as possible, so as not to disrupt the normal operation of the OS. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |