#Macports or fink mac os x#
#Macports or fink install#
#Macports or fink upgrade#
#Macports or fink download#

Once a native Mac OS X interface is available, this process will become much simpler. You now have some new commands: 0launch, which takes the URL of a program and runs it, andĠinstall, which provides access to other features. $ sudo installer -pkg ZeroInstall.pkg -target / After the installation

#Macports or fink install#

You can install the ZeroInstall.pkg bundle with Installer.app, which will use system python and install requirements like GnuPG.pkg and PyGTK.pkg: $ jhbuild -m $PWD/gtk-osx-zero-install.modules build meta-zero-install Bundle installation You can install the gtk-osx-zero-install.modules with GTK-OSX's JHBuild using this command, which will install requirements like gnupg and pygtk: $ sudo fink install zeroinstall-injector Mac OS X/Quartz You can install the zeroinstall-injector package in Fink using this command, which will also install requirements like python26, gnupg, gtk+2, and pygtk2-gtk-py26: $ sudo port install zeroinstall-injector Fink installation You can install the zeroinstall-injector package in MacPorts using this command, which will also install requirements like python26, gnupg, gtk2 and py26-gtk: The bundle installs GnuPG and PyGTK (including PyGObject) and their dependencies,įor Mac OS X 10.5 or later using Python 2.6 (download it from if needed). So if you want to get started quickly the easiest way is the Bundle: ZeroInstall.pkg Or for its BSD sub-system Darwin (using X11) by using either of MacPorts or Fink.Ĭurrently using MacPorts, Fink or JHBuild all require compiling from source code, You can install Zero Install for regular Mac OS X (Quartz) with JHBuild or Bundle, Manager”, to handle building both it and the dependencies (mentioned above) for you: The easiest way of installing Zero Install and its requirements is by using a “package Note: the last version to support Python 2.5 was 0install 1.0

PyGObject/PyGTK (2.12 or later needed for CLI/ GUI).

GObject/GTK (2.12 or later needed for CLI/ GUI).

GnuPG (to check the digital signatures).

Python (version 2.6 or later is needed).Guess it does.This is the older (but better tested) version of 0install.Ĭonsider trying the newer OCaml version (faster, but less well tested).Ġinstall 1.16 is written entirely in Python, so installing from source is quite simple. Now, when everything goes right with macports, it goes *really* right.Â You can install a very up-to-date version of the Gimp, with a proper Mac application bundle, with some of the coolest new plugins (liquid rescale, RAW support via ufraw) and with the ability to access a wide variety of scanners via xsane, all built in.Â That’s exquisitely cool.īut when things go wrong, there’s not much you can do about it, and the hassle you have to go through compiling even when things are going right is a complete pain.Â This ain’t Gentoo, kids.Â It’s a staid operating system for people who don’t want to invest the time and pain that a true open source operating system demands.Â Does it have to be this way?

#Macports or fink download#

It’d be nice if you could just download binary packages from a central repository like you can with most Linux package management systems, and not have to compile them all yourself.Â It used to be possible to do that with fink, an alternative to macports, but in doing so you only got the “stable” (read: ancient and crusty) versions of the packages.Â For the “unstable” (read: created this millennium) versions, you had to compile them yourself, and if you wanted *any* unstable packages, you pretty much had to use allÂ unstable packages… and fink’s set of packages is smaller and less up-to-date than macports’s, so you were screwed. The big Macports thing is: you compile everything yourself.Â This gives you great flexibility if you want some unusual variant of a program.Â But the 95% of the time that you don’t, that you want a standard version of the program just like everybody else’s… tough.Â You’re compiling it yourself no matter how long it takes.

#Macports or fink upgrade#

Random Bits and Pieces: MacPorts are Fatally Flawed gives a good list of reasons why MacPorts sucks.Â I wanted to upgrade the Gimp to the latest and greatest, and I put the wrong flag into the upgrade command and it’s taken all damn day and upgraded nearly every port I had, so far, except the Gimp itself.Â Ports I had forgotten I ever installed.Â Compiling, compiling, compiling.Īnd I didn’t *know* I’d screwed up because sometimes even when you do everything *right* it goes nuts like that.