OS X Tiger still including ruby 1.6

Actually, I think the first question is:

Who do we talk to to first ensure that the information starting this panic is correct?

No offense to the OP, but the original information seems quite unsubstantiated. I had previously heard (from unreliable sources) that Tiger *did* include 1.8

···

________________________________

From: Carl Youngblood [mailto:carl.youngblood@gmail.com]
Sent: Mon 11/1/2004 1:26 PM
To: ruby-talk ML
Subject: Re: OS X Tiger still including ruby 1.6

The question is, who do we talk to to change it?

On Tue, 2 Nov 2004 05:08:50 +0900, Phil Tomson <ptkwt@aracnet.com> wrote:

In article <e5ed7b69041101112361adf896@mail.gmail.com>,
Carl Youngblood <carl.youngblood@gmail.com> wrote:
>I'm not sure who to talk to about this, but in my correspondence with
>some of the Apple developers on the carbon-dev mailing list, I have
>discovered that the current beta release of OS X Tiger is still using
>Ruby 1.6. We should really remedy this situation.
>

Tiger still having 1.6 would be really bad. When are they looking to
release the Tiger? Seems I heard something about February 2005. There
_should_ be enough time to get it changed before then.

Phil

Apple pulls the latest stable from OSS projects it includes at a fixed point
in time (and I don't know where that is for Tiger). I interacted with Apple
during the Panther development cycle and that is what they told me. So,
based on that it will be 1.8 at least, if not 1.8.1. It _should not_ be
1.6.8.

During the Panther cycle I tried hard to get 1.8.0 in and the Apple Darwin
folks really tried, but it was just too late into the release cycle. Apple
does care about these things, and they are on top of it.

No one in the Tiger beta is supposed to disclose features in the beta. The
Darwin source is the foundation of Tiger though, so that is a good place to
watch.

Best,

Rich

···

On 11/1/04 4:59 PM, "Gavin Kistner" <Gavin.Kistner@refinery.com> wrote:

Actually, I think the first question is:

Who do we talk to to first ensure that the information starting this panic is
correct?

No offense to the OP, but the original information seems quite
unsubstantiated. I had previously heard (from unreliable sources) that Tiger
*did* include 1.8

________________________________

From: Carl Youngblood [mailto:carl.youngblood@gmail.com]
Sent: Mon 11/1/2004 1:26 PM
To: ruby-talk ML
Subject: Re: OS X Tiger still including ruby 1.6

The question is, who do we talk to to change it?

On Tue, 2 Nov 2004 05:08:50 +0900, Phil Tomson <ptkwt@aracnet.com> wrote:

In article <e5ed7b69041101112361adf896@mail.gmail.com>,
Carl Youngblood <carl.youngblood@gmail.com> wrote:

I'm not sure who to talk to about this, but in my correspondence with
some of the Apple developers on the carbon-dev mailing list, I have
discovered that the current beta release of OS X Tiger is still using
Ruby 1.6. We should really remedy this situation.

Tiger still having 1.6 would be really bad. When are they looking to
release the Tiger? Seems I heard something about February 2005. There
_should_ be enough time to get it changed before then.

Phil

I based my supposition on the fact that a developer on the carbon-dev
mailing list who appeared to be from Apple said he was running on the
Tiger beta release and when I gave him a script that used Ruby/DL it
croaked on the require 'dl' line. After upgrading to Ruby 1.8.1 it
was fixed. So I assumed that Tiger was shipping with an old version.
I admit this is not a bulletproof supposition.

···

On Tue, 2 Nov 2004 06:59:35 +0900, Gavin Kistner <gavin.kistner@refinery.com> wrote:

Actually, I think the first question is:

Who do we talk to to first ensure that the information starting this panic is correct?

No offense to the OP, but the original information seems quite unsubstantiated. I had previously heard (from unreliable sources) that Tiger *did* include 1.8

I've got it from good authority that it will ship with 1.8.1.

···

--
  Steven
"The beauty of our national parks is awe-inspiring. Except for Jellystone.
I drove through there once, and it was just the same tree, rock, and picnic
bench going by in the background over and over."