3 ms·
I have used "real" package management, both on Linux and Mac OS X, and for native Mac OS X applications it's largely unnecessary. I rarely run into OS X apps th
by tlrobinson 19y ago
I have used "real" package management, both on Linux and Mac OS X, and for native Mac OS X applications it's largely unnecessary. I rarely run into OS X apps that require I install a bunch of dependencies, and most OS X applications these days check for updates on their own. For those that don't there's AppFresh: http://metaquark.de/appfresh/ http://metaquark.de/appfresh/
However, I do agree the method "fails miserably when what you are installing is not an application." MacPorts and Fink are decent solutions, though I admit they could be much better.
- rbanffy 19y agoI really don't think that duplicating libraries (a requirement for OSX-like .App bundles with no external dependencies) or apps checking and self-updating by app-specific methods is a good solution either. For every duplicated library, you introduce the security and stability problems of that specific version, each will have to be addressed by the application provider, who may or may not be interested in the latest developments in the libraries it uses, instead of the original software developer. This thing can grow nasty in no time.