The Overall Reasoning for Portage on OS X

I recently had some problems with my iBook and some of that was due to the power management driver that fragged my harddrive. My iBook was sent to Apple and my harddrive was replaced. I lost about a years worth of digital photos (on my Apple partition), school papers I wanted to keep, development documents that I was in the process of reading, important emails, etc.

I don't really "blame" gnu/linux for that experience - heck, I still use Gentoo on my desktop machine - but, I felt that if $capable of using my favorite free/open source programs and tools on my iBook under darwin [which uses the Apple drivers for sound, power management, etc], well - I could be a happy, crash-worry-free, camper. So, I went back to Fink.

After trying that approach, I found many of the packages were too old for my perferences and most of them only ran on OS X 10.2.* [I was running 10.1.* at the time]. So that was a problem and I looked around at the gnu/linux ports project the gnu/darwin ports project and the package manifests were again, a little too old for my preferences. I also remember finding a couple of other tools that did fink-type work and I wasn't overly content to have to figure out the installation process for the system and then to use the system itself would require a learning curve. That's when it dawned on me to look at Portage as a possible solution.

I checked the Gentoo Forums site and found a thread for GentooBSD. I read that forum and the idea seemed more practical, not$involve less learning curve on my part and a little editing for the ebuilds I wanted to install. So, I continued looking for some more data on moving portage and found an article about using portage on non-Gentoo systems. That's were I stopped looking and started editing.