MacLibre

Don't forget about DarwinPorts...

Installing isn't the only thing a package manger does. It also updates.

Sure you can install things from scratch quite easily on OS X. You can install things a bit less easily in Linux too. The great part about a package manager is that with two commands you can update all programs on your OS. I don't need to go to firefox.org and openoffice.org and yetanotheropensourceapplication.org. You just sync and update.

Imagine if software update didn't just update your Apple created software but all the software on your system, that's what a (good) package manager does.

Just what we need, another method of installing stuff. We already have the best install method; drag and drop (too bad all developers don't use it). And we also have the package installer. This way will just add inconsistancy to the process. Besides, this thing wants your admin password to do the install; not necessary.

Personally, I can see the reason for this on Linux, but for Mac OS X? I think the projects need to conform to the more standard way of installing Mac applications... drag the app to the Applications folder. Done. Bundle the dependencies and an .app package folder.

this is cool and all but like most open source project why does there need to be 4 things trying to do one. we have fink, macports and now this. in my mind to have a visual package manager is a good thing but it should be able to integrate with already developed systems so that the developer can focus on the manager itself instead of the ports.