Gentoo for Mac OS X Released
joeljkp writes "According to today's Gentoo Weekly News, Gentoo has released a new project: Gentoo MacOS (sic). This new distribution adds Portage, Gentoo's package manager, to Mac OS X, among other things."
← Back to Stories (view on slashdot.org)
how exactly is this a problem for Apple?
This means (sorta, as in 'soon') that a Mac-user will be able to rebuild their own OSX box, using the Gentoo scripts, and still be able to maintain compatability with all OSX apps.
In other words, a 'better build system: a public one' has been unleashed on a commercial operating system, so that - separate from the company itself - alternative builds of the OS can be done, publically.
Why is this good? Because with Gentoo you can take personal risks that Apple can't. Gentoo allows you to build a system "Just for You", whereas Apple have to compile/link things "For Everyone".
Expect to see highly-tuned Gentoo boxes running GentooMacOS in the future, smokin' 'Factory OS' setups. I'll be digging into this a bit further, next point release sort of thing, and if I get the same results out of applying Gentoo to my OSX machine as I have with my Linux boxes, I'm excited. I may man I can put off a hardware upgrade or two and just 'Take Things To The Next Level' on my aging Powerbook...
Oh, and in case you think Apple should be 'worried about' this, it seems to me that they already get the point. With all the OS releases they've been doing lately, and the upgrades/improvements in the one area 'open source' is lacking: usability, and it seems to me that they're positioned well to be 'competing with the Open Source Base'
; -- the corruption of government starts with its secrets. a truly free people keep no secrets. --
gentoo's strenth is its' ability to squeeze 0.0008 percent more processing power out of your 2.4ghz computer
Actually, that is not Gentoo's primary strength. Its strength is from the amount of flexibility that portage provides for package dependency. With binary-oriented distributions, you are forced to use the same configuration settings that were chosen by the package maintainer. Portage has the concept of "USES", which is basically a list of flags that the build uses to figure out what options to use during compilation. For example, many packages can be integrated with GNOME. I don't use GNOME. With other distributions, if the package was built with GNOME dependencies, I'd be forced to install GNOME. If the package was built without GNOME, some GNOME user wouldn't be able to take advantage of GNOME-specific features. With Portage, you can specify via the USES variable whether or not you want to have a dependancy on GNOME or not. As a side effect, you get the CPU-optimization "for free".
Compared to a couple days to get the same results with Gentoo, which is an outstanding distro, but not the distro to break Linux onto the mainstream desktop. Any casual PC user who has built a gaming PC or even tinkered around with his Dell could get Mandrake up and usable in less than an hour, Gentoo however is another story. Of course Gentoo wasn't aimed at that market, but the parent poster can't possibly paint Gentoo as easy to install and not expect some rebuttals.
I could well just be missing something, but I've had a lot of problems with the selection granularity in fink -- e.g. trying to build x-chat without dragging in all of GNOME. USE flags would be a very nice alternative.
What I'm listening to now on Pandora...
One of the most awesomeliest things about Fink is that it installs everything in root /sw, no exceptions (i.e. /sw/bin, /sw/usr/lib, etc). That means you don't have to worry about contaminating the Apple-controlled parts of the OS, and uninstalling all customizations is just a matter of trashing /sw. I would never even think of installing anything in /usr or /usr/local (because it "belongs" to Apple).
Does Gentoo MacOS do the same thing? If not, why not????