- #UNINSTALL MACPORTS PACKAGE MAC OS X#
- #UNINSTALL MACPORTS PACKAGE MAC OS#
- #UNINSTALL MACPORTS PACKAGE INSTALL#
Uninstall MacPorts: rm -rf /opt/local/ /Applications/MacPorts/ /Library/Tcl/macports1.0/ /Library/LaunchDaemns/org.macports.* Uninstall (deactivate) ports: port uninstall (deactivate) emacs Upgrade all (one) outdated ports: port upgrade outdated (emacs) Search available ports: port search emacs List all available (installed/outdated) ports: port list (installed/outdated) I have used ’emacs’ as an example for package name.
You will need ‘sudo’ for most of these commands, i.e., when write/execute permissions are needed. But this should be all you need if you are a basic user. The MacPorts Guide talks about all of these commands (and more) in more detail. And have fun!īasic Commands: The average Macports user needs only a handful of commands to install, upgrade, and remove MacPorts.
#UNINSTALL MACPORTS PACKAGE INSTALL#
That is basically it! Then go to the MacPorts install page, download the dmg, and start building any (or all) of its 7015 ports (in 92 different categories).
#UNINSTALL MACPORTS PACKAGE MAC OS#
Pre-requisites: Assuming you have a Mac OS X, get the latest versions of X11 and XCode. Again, if you have the expertise, you can always install fink packages in your Macports system as both are open source. The good news is that the Macports port library is becoming as extensive as the fink library despite its late start. While it is not necessary to keep your packages updated by the day (or the month), it is always nice not to have to wait months for a fix. The other (big) advantage of Macports is its more active developer base hence, the various packages tend to get updated quicker. In my experience it also takes 3-4 attempts before you get Fink installation right. Of course, you can build ports from fink in MacPorts and vice versa - it just takes a little more effort. For this reason MacPorts uses less hard disk space as well. The caveat being that while Fink installs most of the basic tools and libraries that will be needed in the future and ‘completely’ builds the Unix environment, MacPorts only creates the basic directory structure during installation. It takes a couple minutes, which is miniscule compared to the ~45 mins needed for Fink. For e.g., if you only need a handful of applications (and not the entire Red Hat system), MacPorts is much easier and faster to install. While both systems serve the same purpose, there are differences that make one or the other more appealing. Over the past few years, MacPorts has developed as a very nice alternative to Fink in the last couple years. For long, the open-source project Fink has long been our savior.
#UNINSTALL MACPORTS PACKAGE MAC OS X#
However, as the Mac OS X is built on X11, there is no need to install a complete UNIX OS, it does require quite a bit of work to make your machine Unix-capable. Apple does not support or maintain its Terminal or X11/XQuartz applications it is rather supported by an independent group of developers (see XQuartz wiki). While the Mac OS X provides us easy access to the much-beloved terminal, by itself, it is very limited.
0 kommentar(er)
