3 ms·
>> On a new linux machine I can apt-get most anything, but if I do need to compile something I just apt-get build-essentials and I'm ready to go, on OSX you hav
by _delirium 15y ago
>> On a new linux machine I can apt-get most anything, but if I do need to compile something I just apt-get build-essentials and I'm ready to go, on OSX you have to download a DVD just to be able to compile stuff from source.
> Darwin ports? Fink?
I've used both for the past near-decade (fink for 4 years, now macports for the past 3), along with a Debian desktop, and they're much worse imo. They do the job sort of, but it's a mess. Stuff just outright breaks much more often than even in Debian 'unstable'; you'll install a package and it'll fail to compile, fail to link, a script will die, etc. Dependencies are a mess, especially as regards versions of interpreted languages (python/perl/etc.), and anything that interacts with X11 tends to be flaky. And the use of binary packages is still very spotty, so a simple install, if it pulls in big library dependencies, might spawn an hour or two of compilation, rather than a few minutes of installation.
It gets the job done somewhat, but I'm not really happy with the situation overall; for many things I prefer to use a Debian VirtualBox install, despite that also having some awkwardness.
- robin_reala 15y agoDump both macports and fink and use Homebrew instead: http://mxcl.github.com/homebrew/ http://mxcl.github.com/homebrew/
- kylewpppd 15y agoI fail to see how anyone can recommend homebrew as a viable solution to package management on OS X. You have to compile everything. Coming from apt-get or yum makes brew, port, and fink look like a joke.
- dasil003 15y agoIf you're installing that many large UNIX packages I'm going to go out on a limb and suggest that there are probably a lot of reasons you'd be better off on Linux.
- wes-exp 15y agoI'm using both Linux and OS X regularly. Apt is awesome, without a doubt, particularly for the breadth of software available. And on the whole, I agree that Homebrew is considerably inferior. But there is one aspect I'm liking better about the Homebrew/Mac approach. With Homebrew I can have the latest software without a problem, because the OS itself is not so hooked in to the web of package manager dependencies. In many cases on Linux I just wait until the next OS release to upgrade software - because toying with the huge dependency graph is not worth it. Maybe I should switch to a rolling release distro? I haven't tried that. But I do like the ability to upgrade software without so many inter-dependencies.
- randallsquared 15y agoIn many cases on Linux I just wait until the next OS release to upgrade software - because toying with the huge dependency graph is not worth it. Maybe I should switch to a rolling release distro? I haven't tried that. When I most recently used Linux on the desktop, in 2010, I finally grew frustrated enough with Ubuntu's screen management setup (there was no way to get it to respect my wishes for it to turn off the screen completely, until I finally killed the power manager entirely) that I switched to Arch. That was superficially better (stuff mostly worked as advertised), but the rolling release means either keeping up to date and dealing with constant breakage ("Oh, look, the new kernel has a broken driver for my audio card", or "Oh, another update, another few hours troubleshooting Wine. Yay"), or waiting a while and having the update become riskier and riskier. Linux will be ready for the desktop when updating doesn't mean near certainty that something breaks. I realize that things used to be more broken, but when I used Linux as my primary desktop back in 1998-2003, my expectations were lower. Being a Mac user for 5-6 years seriously reduced my patience with troubleshooting random problems just to get all the functionality that the system I'm using claims to provide.
- MatthewPhillips 15y agoYou want to use a distro with an LTS release. Switching to Arch and being surprised that pacman -Syu causes occasional breakage is not a failure of Linux at large.
- m3koval 15y agoBuilding from source isn't necessarily a bad thing: some Linux packages have the same behavior (e.g. Portage, on which MacPorts is based). There are pros and cons to both approaches. Package management is definitely a disaster on OS X, though. Regardless of whether you use Homebrew, Fink, or MacPorts, packages tend to break often. Some of this may be unavoidable: there are enough differences between Linux and OS X that compiling programs developed for Linux for OS X is bound to cause problems.
- X-Istence 15y agoI have been using HomeBrew on Mac OS X and it is miles ahead of where MacPorts and Fink are. Definitely worth a try.
- nupark2 15y agoMiles ahead how? It's the same thing, but written in Ruby instead of Perl (Fink) or Tcl (MacPorts).
- robbles 15y agoHomebrew tries to use the default libs and utilities that come with OS X / Xcode. MacPorts and Fink try to create their own little microcosm of a Linux system complete with all libraries and utilities. They generally seem to fail at this because major packages are broken all the time and conflict in a million little ways with the system ones.
- nupark2 15y agoMacPorts and Fink try to create their own little microcosm of a Linux system complete with all libraries and utilities. That's more like a philosophical (and failure prone) difference that both Fink and MacPorts intentionally abandoned through experience, not really a "miles ahead" difference. Not reproducing Apple's OS dependencies is a nice idea, but let's say I want to use python2.7 with openssl 1.0. Apple only shipped openssl 0.9.8 in Lion. If I mix modules that use OpenSSL 1.0 and OpenSSL 0.9.8, weird stuff happens. Now what? (The answer is: now you have to start reproducing OS dependencies. This only gets worse as the OS dependencies grow more stale). They generally seem to fail at this because major packages are broken all the time and conflict in a million little ways with the system ones. I haven't observed this.