![]() Fink on the other hand is inspired by debians apt-get style and has precompiled packages. I would go with port unless i don’t find any specific package with it. All of its packages are depending mostly on existing Mac version port has a largest selection of packages to install. It will build every package on its own and doesn’t depend on OSx base. You don’t want to care about much and just want the stuff to work. The basic difference between brew and port i see is that, brew leverages most of the functionality from OSX so less time and space to setup. But you can choose which one you can go with. Personally, i have both Homebrew and MacPorts. This enables the packages to work also on mac. Homebrew, MacPorts and Fink The packages are build / developed on Darwin OS which is base for mac. Sort of like a seminar, but with (even) more rude commentary from the audience.Like apt-get for Debian, yum for Red Hat Linux Operating Systems, there are couple of package manager for Mac. Also, Fink follows the Debian distribution idiosyncrasies while MacPorts follows the BSD ports'. From my experience, Fink has much more packages, specially for science, and MacPorts has more recent packages specially for popular stuff like Web development. Commentary on our own research, other mathematics pursuits, and whatever else we feel like writing about on any given day. I use Fink and have been a package contributor to it. Of course, best is to load init.sh at login.Īctually, best practice is to use TikZ and forego xfig altogether …Ī group blog by 8 recent Berkeley mathematics Ph.D.'s. Then that can be clicked on and xfig will be launched correctly. If you run xfig by clicking on an icon, and you don’t run init.sh from login, then you need to create a wrapper script, say “myxfig”, which contains the line that you mention: “#! /bin/sh source /sw/bin/init.sh xfig”. If you use another shell (you should be using zsh, of course), then put it in the correct file. ![]() It's just a system that keeps track of installed ports and maintains dependencies in its own self-contained /opt/local directory (with few exceptions). There are no background processes at all for the MacPorts package installer. The best way is, as Steven Sivek says, to ensure that it is run at login. I can mainly speak for MacPorts, but I'm sure this applies to at least Fink and likely Homebrew as well. So whenever you run anything finky, you should ensure that that script has been called. So there’s a script, /sw/bin/init.sh, which tells the system where to find fink-related stuff. For Helm 3.3 sudo port install helm-3.3 Add the select port sudo port install helm-select This will allow you to choose which version of helm that will appear on your path. However, at some point you want the system to know of its existence otherwise you could never run any programs that fink installed. However macports does download binaries in most cases so how much of this is needed could differ. It does that by installing in the /sw directory. In particular, it tries to make sure that it installs stuff in a way that doesn’t interfere with the existing stuff. (Disclaimer: my iBook no longer runs MacOSX so my information may be out of date)įink does its level best to “play nice” with MacOSX (and that’s a good thing). All credit goes to Alexander Hansen, whomever he may be, for figuring this out. I know very little about what’s going on here, so I won’t try to explain more, but I found quite a number of message boards where this bug was discussed before finding one where it as solved, so I thought it might be useful to disseminate the solution. In summary, if you are in the habit of running xfig by bringing up an X11 terminal and typing “xfig”, you probably want to be typing source /sw/bin/init.sh xfig instead. ![]() This may be done with "make install" in the xfig source directory" You should install the correct version or you may lose some features. I installed xfig using fink, and got the messageĮither you have a very old app-defaults file installed (Fig), I have not seen duplicated dependancies or conflicts, as versioning is at the application level, not the package manager. macports vs fink closed Ask Question Asked 14 years, 6 months ago Modified 14 years, 6 months ago Viewed 2k times 7 Closed. ![]() I have not had a problem with them co-existing. I spent most of the evening struggling with xfig, and want to record this my discovery for anyone else who is having the same problem. I have been successfully running Homebrew and Fink on my Mac Mini (late 2012) through the last 4 OS updates. I got a new Mac laptop last winter, and am still in the process of getting all of my old software installed on it.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |