Almost exactly one year after the idea of porting Portage to MacOS X came up – and the joint Metapkg initiative between Fink, Darwinports and Gentoo took off – a 20-head-strong developer team around Pieter van den Abeele (strategic lead) and Daniel Ostrow (operational) is now ready to release an extraordinary beast into the wild: Gentoo MacOS.
Portage on Mac OS X
About The Author
Eugenia Loli
Ex-programmer, ex-editor in chief at OSNews.com, now a visual artist/filmmaker.
Follow me on Twitter @EugeniaLoli
16 Comments
Do you really need a gui for portage? It’s not difficult to use at all.
No, you’re right, I don’t need a GUI. Some of the other stuff in the todo list is interesting. My main beef with portage is that it seems to not upgrade some packages even if you give it all the recursive all flags you can. That and slowly breaking subtle integration in the desktop world each time you do a full upgrade. I’m learning that that’s more universal than just portage. MEPIS (read: debian) lost it’s mind after a few upgrades. SuSE (ftp) bugs started cropping up. Fedora Core 2 seems to be fairly stable, but most of the updated packages have been fairly minor so far.
When I say “lost its mind” and such, I’m not saying the machine ground to a halt. It more that little things, like the Flash reader, camera, etc would stop working after an upgrade, causing me to have to dive into config files to attempt to get them working again.
Unfortunately, with a pre-setup system for me it’s all of nothing. If it doesn’t work right every time, it’s more trouble to figure out what has broken rather than just doing it yourself in the first place. The problem is there isn’t a document describing what in fedora has been changed, so you can’t recreate the original config.
Interesting, it sounds as if Gentoo MacOS will pack its own version of gcc as an option. Assuming that you keep a current version of gcc, are there going to be binary compatibility issues with older versions os OS X? If I compile app foo on Jaguar w/gcc 3.4 or 3.5, will it run?
Gentoo has a mechanism, called slots, that allows one to install different versions of a package on a Gentoo system. You can install, GCC version 3.4, 3.5 and 3.6 etc, on a Gentoo box and switch between any of them using gcc-config, if I remember clearly.
It is not uncommon for many users to have 3 different versions of a package on their system for testing purposes. And if you read the gentoo documentation dilligently enough, I doubt you’d be “hosing” your system. I haven’t hosed my in three years.
Anyone know how the Gentoo BSD effort is going?
I’ve tried pkgsrc before, on Solaris/SPARC. It’s a very easy, simple, portable ports systems from guys at NetBSD team. If you really want to have BSD package system from a BSD team, then you really need this.
Check the website of pkgsrc at
Of course, they have MacOS X binaries on download page too. And the docs are awesome.
BSDero
emerge -pvuD world
That updates the whole system as well as dependencies to each package. Secondly, even after updating your system, portage never touches your config files.
So I don’t know what config files you where delving into to restore your system after an update. Your other remarks are all too vague, I can’t be of further assistance.
“My main beef with portage is that it seems to not upgrade some packages even if you give it all the recursive all flags you can. That and slowly breaking subtle integration in the desktop world each time you do a full upgrade. I’m learning that that’s more universal than just portage.”
I’ve had my current Gentoo installation since October 2002, and it’s still runs perfectly. Unless something of an unforseen catastrophic nature occurs, I plan to continue using this installation as long as possible.
I also keep most packages @ x86 (except for those in package.keywords), I never use emerge -u world, and I make sure I keep tabs on the files on my system with some handy scripts found in the forums (such as dep and cruft).
If this turns out to work well… it means very good things for OSX, hell I might even buy a mac
Not long ago, maybe 6 months or a year… yes you were right, even when you ran an emerge -pUD world, it would miss upgrading some packages.
That is no longer true, however. I double check often (by making a fake /var/cache/edb/world file with qpkg), and emerge with the U and D flags has not missed a single upgradeable package in ages.
I also keep most packages @ x86 (except for those in package.keywords), I never use emerge -u world,
If you use package.keywords it is better to use the “-u” flag as opposed to the “U” flag.
Thanks for the tip. The big problem I remember was my camera in KDE: one day it worked, after an upgrade, it didn’t. Figured out there was something funky with libgphoto that if I installed it from portage, it didn’t find my camera. Installed from source (save version it worked fine). I remember my mouse failing after an upgrade (USB logitech), and of course the nvidia binary driver having to be uninstalled and reinstalled[0] after emerge world, which means I can’t get back into X, since my monitor (SGI 1600sw, via DVI) doesn’t play nice with the open nv driver.
[0] I was *very* unhappy about that. We’re not dealing with Windows 95, after all.
“If you use package.keywords it is better to use the “-u” flag as opposed to the “U” flag.”
I meant I don’t use either. I do all my updating by hand (i.e. individual packages). This way I can keep track if any package gives me problems and back out easily.
I meant I don’t use either. I do all my updating by hand (i.e. individual packages). This way I can keep track if any package gives me problems and back out easily.
Very prudent. I use the “-u” switch but only with “-p”. From there I usually emerge packages seperately.
Maybe if they come through with the todo stuff (full system builds, gui, etc), it’ll be worth switching from