On Nov 29, 2007, at 7:01 AM, Andreas Korth wrote: > > On 28.11.2007, at 19:36, Noah M. Daniels wrote: > >>> Interestingly, the words "major problems" and "Leopard" coincide a >>> lot >>> lately. > >> For what it's worth, I've had zero problems with the Apple-supplied >> ruby, rails, etc... > > Frankly, knowing that everything works well for others isn't worth > much to people who _are_ having problems ;) > > But it appears to be a common reaction – especially in the Apple > community.
Point taken, but I was responding to the poster's statement that they'd avoided the apple-supplied Ruby. > > > You must have a different understanding of 'getting it right'. > Here's what I got when I entered 'ruby -v' or 'gems' into the > console of a fresh 10.5 install: > > -bash: ruby: command not found > That's very strange, but just sounds like a path issue. > After getting it to work eventually, a 'gem update --system' just > wrecked the whole Ruby installation. At that point I just gave up > and installed Ruby/Gems and Rails via Macports. > Yes, this one is a known issue. See these links: http://discussions.apple.com/thread.jspa?threadID=1200950&tstart=0 http://discussions.apple.com/thread.jspa?threadID=1202925&tstart=0 > One thing I'd really like to know is how one is supposed to update > the Ruby/Rails packages which shipped with Leopard. I had no chance > to check, but are they still shipping Rails 1.1.2? I bet that Apple > isn't going to update Ruby during the whole lifetime of Leopard. > Anything else would be a big surprise. > It comes with rails 1.2.3, and gem update rails updates it to 1.2.5 (well, now 1.2.6) just fine. > So here goes my advice again: Use Macports. Do not use whatever > Apple ships. I disagree in the most friendly way possible :) _______________________________________________ Ferret-talk mailing list [email protected] http://rubyforge.org/mailman/listinfo/ferret-talk
