Thanks, Rob.  Did you just do a straight upgrade or did you take the
archive and install route?

Ken

On Apr 7, 1:25 pm, "Rob Kaufman" <[EMAIL PROTECTED]> wrote:
> Hi Ken,
>   After upgrading my box to Leapord (Macbook Pro), my Macports installed
> software continued to work just fine.  You millage may vary, but no matter
> what you can still get old version of Rails from Rubygems so you shouldn't
> have to big a heart ache if you need to rebuild your Macports code.  Seems
> like the biggest problem people have had via upgrading is if they have
> Logtech drivers or ApplicationEnhancer installed (as described 
> herehttp://daringfireball.net/2007/10/blue_in_the_face)
>
> Rob
>
> On Mon, Apr 7, 2008 at 1:18 PM, Ken <[EMAIL PROTECTED]> wrote:
>
> > I installed the Xcode Tools; followed by MacPorts; and then used
> > MacPorts to install apache2, mysql, subversion, ruby, rb-rubygems,
> > etc; and then I did gem installs for rake, rails, capistrano and
> > mongrel.
>
> > Thanks, Ken
>
> > On Apr 7, 12:04 pm, "Matt Aimonetti" <[EMAIL PROTECTED]> wrote:
> > > how did you install rails + ruby ?
>
> > > -Matt
>
> > > On 4/7/08, Ken Hudson <[EMAIL PROTECTED]> wrote:
>
> > > > Hi everyone,
> > > > I'm going to be upgrading my machine from Tiger to Leopard in the next
> > few
> > > > days, and I was wondering what kind of impact this will have on my
> > existing
> > > > Rails install. I currently have Rails 1.2.6 and I need to keep it for
> > one of
> > > > my applications for awhile longer. Also, installed is Ruby 1.8.6 and
> > > > Capistrano 1.3.1. I know Leopard has more current versions and I'm
> > > > wondering if the Leopard install will leave the current versions in
> > place or
> > > > not. Which upgrade method do you all recommend (i.e., Upgrade Mac OS
> > X,
> > > > Archive and Install, or Erase and Install)?
>
> > > > Thanks!  Ken
--~--~---------~--~----~------------~-------~--~----~
SD Ruby mailing list
[email protected]
http://groups.google.com/group/sdruby
-~----------~----~----~----~------~----~------~--~---

Reply via email to