# Leopard 10.5.3 breaks MacPort Rails

**URL:** <https://www.ruby-forum.com/t/leopard-10-5-3-breaks-macport-rails/139174>\
**Category:** Rails\
**Created:** [June 1, 2008, 3:29am UTC](https://www.ruby-forum.com/t/leopard-10-5-3-breaks-macport-rails/139174 "2008-06-01T03:29:46Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![starmaerker](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/s/e9bcb4/32.png) [@starmaerker](https://www.ruby-forum.com/u/starmaerker)\
**Post date:** [June 1, 2008, 3:29am UTC](https://www.ruby-forum.com/t/leopard-10-5-3-breaks-macport-rails/139174/1 "2008-06-01T03:29:46Z")

</div>

If you’ve installed Ruby and Rails using mac ports, be aware that  
installing 10.5.3 will install new versions of ruby and rails, which  
will hide your mac ports versions of rails.

I had to go into /usr/bin and reset/delete a whole bunch of symlinks.

Just be aware.

---

<div class="post-metadata">

**Author:** ![starmaerker](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/s/e9bcb4/32.png) [@starmaerker](https://www.ruby-forum.com/u/starmaerker)\
**Post date:** [June 1, 2008, 7:15am UTC](https://www.ruby-forum.com/t/leopard-10-5-3-breaks-macport-rails/139174/2 "2008-06-01T07:15:32Z")

</div>

I haven’t upgraded yet, but I doubt there’s a problem with 10.5.3 and  
Ruby. Instead, I think there may just be an issue with your path. As  
long as you have /opt/local ahead of /usr/bin on your path, you should  
be able to have both Ruby installs co-exist peacefully.

Regards,  
Craig

---

<div class="post-metadata">

**Author:** ![starmaerker](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/s/e9bcb4/32.png) [@starmaerker](https://www.ruby-forum.com/u/starmaerker)\
**Post date:** [June 1, 2008, 9:26am UTC](https://www.ruby-forum.com/t/leopard-10-5-3-breaks-macport-rails/139174/3 "2008-06-01T09:26:35Z")

</div>

Hi, I agree with Craig because if you have your PATH setup properly both  
should be able tocoexist. For example, I have the following in my  
.profile:

export  
PATH=/opt/local/bin:/opt/local/sbin:/opt/local/apache2/bin:${PATH}

Please follow the instructions on the MacPorts site because it’s there  
in  
section 2.4:

[http://guide.macports.org/](http://guide.macports.org/)

Good luck,

-Conrad

On Sat, May 31, 2008 at 10:14 PM, Craig D.  
[removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid)

---

<div class="post-metadata">

**Author:** ![starmaerker](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/s/e9bcb4/32.png) [@starmaerker](https://www.ruby-forum.com/u/starmaerker)\
**Post date:** [June 1, 2008, 1:01pm UTC](https://www.ruby-forum.com/t/leopard-10-5-3-breaks-macport-rails/139174/4 "2008-06-01T13:01:26Z")

</div>

There is however an issue with drb (see  
[http://blade.nagaokaut.ac.jp/cgi-bin/scat.rb/ruby/ruby-talk/303297](http://blade.nagaokaut.ac.jp/cgi-bin/scat.rb/ruby/ruby-talk/303297))

Fred

---

<div class="post-metadata">

**Author:** ![starmaerker](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/s/e9bcb4/32.png) [@starmaerker](https://www.ruby-forum.com/u/starmaerker)\
**Post date:** [June 3, 2008, 2:08pm UTC](https://www.ruby-forum.com/t/leopard-10-5-3-breaks-macport-rails/139174/5 "2008-06-03T14:08:32Z")

</div>

Just a FWIW… Leopard’s Ruby has always worked fine from the start and  
not  
needed Macports management. Just one less headache on my end. YMMV

RSL

On Sun, Jun 1, 2008 at 7:00 AM, Frederick C.  
[removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid)

---

<div class="post-metadata">

**Author:** ![starmaerker](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/s/e9bcb4/32.png) [@starmaerker](https://www.ruby-forum.com/u/starmaerker)\
**Post date:** [June 3, 2008, 2:23pm UTC](https://www.ruby-forum.com/t/leopard-10-5-3-breaks-macport-rails/139174/6 "2008-06-03T14:23:57Z")

</div>

Hi,

On Jun 3, 1:07 pm, “Russell N.” [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) wrote:

> Just a FWIW… Leopard’s Ruby has always worked fine from the start and not  
> needed Macports management. Just one less headache on my end. YMMV

That’s my experience too. Leopard’s ruby also works with dtrace, and I  
couldn’t get that to work with MacPorts ruby. It’s been a couple of  
months since I tried it though.

Jon