So what little genie whispered that magic into your ear? Thanks for passing it on though. I don't want to say how long I spent puzzling through the mkmf / extconf code trying to figure how to pass that sucker in. Is this a general RoR convention or what?
Rick On Dec 3, 12:25 am, Frederick Cheung <[EMAIL PROTECTED]> wrote: > On Dec 3, 9:23 am, Rick <[EMAIL PROTECTED]> wrote: > > > Well, that didn't seem to go too well. It seems that somewhere in the > > mkmf / extconf.rb soup the actual location of the mysql home has > > gotten lost. The only way this will work is if mysql is installed in / > > usr/local, the default for the distributed precompiled version is to > > go in /usr/local/mysql. > > so what do you think about that? > > Since day one i've always done > > gem install mysql -- --with-mysql-config=/usr/local/mysql/bin/ > mysql_config > > Fred > > > Rick > > > On Dec 2, 11:24 pm, Frederick Cheung <[EMAIL PROTECTED]> > > wrote: > > > > On Dec 3, 2:20 am, Rick <[EMAIL PROTECTED]> wrote: > > > > > Hey Joshua and Fred, > > > > > I agree with the general statement that installing the mysql gem has > > > > gotten harder. In fact, the only way I've been able to do it is by > > > > pulling in the mysql-ruby source from tmtm.org, modifying the > > > > extconf.rb file, and building my own gemspec. > > > > > I have been able to install versions from 2.7.0 through 2.8 on Mac OS > > > > X under Ruby 1.8.7p72, Rails 2.2.2, Gem 1.3.1. I don't have access to > > > > a Windows system of any kind however so I don't know how portable my > > > > change is. > > > > If you're dealing with the gem that is nothing to do with the rails > > > version. The ruby version might have an impact though (I've been > > > staying away from 1.8.7). > > > Personally with ruby 1.8.6 I've had zero problems. It's a bit of a > > > coincidence timing wise but over the past week I've setup/helped setup > > > 3 machines for our developers (2 macs, one ubuntu) and they've all > > > gone swimmingly > > > > Fred > > > > > Rick > > > > > On Dec 2, 12:37 pm, Joshua Partogi <[EMAIL PROTECTED]> wrote: > > > > > > I was talking about the mysql ruby driver is not come bundled and > > > > > installing it manually is not easy too. > > > > > > On Dec 3, 12:04 am, Frederick Cheung <[EMAIL PROTECTED]> > > > > > wrote: > > > > > > > On Dec 2, 12:50 pm, "Joshua Partogi" <[EMAIL PROTECTED]> wrote: > > > > > > > > Hi all, > > > > > > > > I've been searching through the list about configuring MySQL > > > > > > > adapter > > > > > > > on Rails 2.2, and it seems that this question is asked over and > > > > > > > over > > > > > > > again without any solution :-D Why did Rails 2.2 made configuring > > > > > > > the > > > > > > > mysql driver so difficult? Why is it a move backward in Rails > > > > > > > 2.2? Why > > > > > > > isn't there any documentation on this at all while people keep > > > > > > > asking > > > > > > > this same question over and over again? > > > > > > > Are you talking about the removal of the pure ruby driver ? > > > > > > I haven't moved most of the stuff I do to rails 2.2, but creating a > > > > > > rails 2.2 app from scratch basically just worked in the same way as > > > > > > it > > > > > > has ever done. (or are you talking about the change from mysql as a > > > > > > default to sqlite3 ?) > > > > > > > Fred > > > > > > > > Cheers. > > > > > > > > -- > > > > > > > Not by might nor by power, but by His Spirit. > > > > > > > > Read my blog:http://joshuajava.wordpress.com/ > > > > > > > Follow me on twitter:http://twitter.com/jpartogi --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
