[gentoo-dev] Ruby: depreciating 1.6.8 in favour of 1.8.0

[gentoo-dev] Ruby: depreciating 1.6.8 in favour of 1.8.0

[Tom Payne]

The new stable version of Ruby, 1.8.0, was released a few days ago.

I would like to update all of dev-ruby to use 1.8.0, and depreciate 1.6.8
completely. Reasons for depreciating 1.6.8 are:

1) AIUI 1.6.8 is now dead and will not be maintained.

2) There are a number of (small) language changes that mean that will cause
some 1.6.8 to break under 1.8.0. This means that maintaining 1.6.8 packages
alongside 1.8.0 packages will be problematic.

3) 1.8.0 now includes a number of packages that were previously distributed
separately (e.g. rexml, syck, optparse, webrick, racc, strscan, eruby,
runit, xmlrpc).  Creating virtuals for all of these packages so that users
have the option of 1.6.8 or 1.8.0 would be a nightmare, especially since
portage does not officially support versioned virtuals.

Switching to 1.8.0 will also have downsides:

1) Forcing 1.6.8 users to upgrade may break their code.

2) Older 1.6.8 packages will no longer be supported.

Comments? Complaints?

Unless there is a huge cry of "keep 1.6.8!" I will being the migration on
Mon 18 Aug.

Cheers,

Tom

--
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] Ruby: depreciating 1.6.8 in favour of 1.8.0

[Ferris McCormick]

On Sun, 10 Aug 2003, Tom Payne wrote:

> The new stable version of Ruby, 1.8.0, was released a few days ago.
> 
> I would like to update all of dev-ruby to use 1.8.0, and depreciate 1.6.8
> completely. Reasons for depreciating 1.6.8 are:
> 
> 1) Forcing 1.6.8 users to upgrade may break their code.
> 
> 2) Older 1.6.8 packages will no longer be supported.
> 
> Comments? Complaints?
>
I've put it on one system to try it officially (I've been playing
with various release candidates for one particular application which
really wants the newer gc code).  It builds and installs on sparc,
and runs simple tests.  I'll start rebuilding packages over the next
few days on this system and let you know how it goes.

One comment:

The "You might have to re emerge vim" comment needs to be made very clear;
there doesn't seem to be any "maybe" about it (if you use vim+ruby), 
because the rebuild of vim is required because of the libruby version
change.

Regards,
Ferris

 
> Unless there is a huge cry of "keep 1.6.8!" I will being the migration on
> Mon 18 Aug.
> 
> Cheers,
> 
> Tom
> 
> --
> gentoo-dev@gentoo.org mailing list
> 

--
Ferris McCormick (P44646, MI) <fmccor@inforead.com>
Phone: (703) 392-0303
Fax:   (703) 392-0401


--
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] Ruby: depreciating 1.6.8 in favour of 1.8.0

[Aron Griffis]

[-- Attachment #1: Type: text/plain, Size: 754 bytes --]

Ferris McCormick wrote:	[Sun Aug 10 2003, 12:31:07PM EDT]
> The "You might have to re emerge vim" comment needs to be made very clear;
> there doesn't seem to be any "maybe" about it (if you use vim+ruby), 
> because the rebuild of vim is required because of the libruby version
> change.

That message was actually for another reason: Some library internals
changed in 1.8.0_pre5 which required vim to be remerged, even if it had
previously been linked against 1.8.0_pre4.

Nonetheless, you're right that the message could be updated, so I fixed
it.  Now it says:

* 
* Warning: Vim won't work if you've just updated ruby from
* 1.6.8 to 1.8.0 due to the library version change.
* In that case, you will need to remerge vim.
*

Aron

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-dev] Ruby: depreciating 1.6.8 in favour of 1.8.0

[Mamoru KOMACHI]

Hi,

At Sun, 10 Aug 2003 16:22:52 +0200,
Tom Payne wrote:

> Switching to 1.8.0 will also have downsides:
> 
> 1) Forcing 1.6.8 users to upgrade may break their code.

Why don't you create ruby-shim ebuild for 1.6.8 users to keep using
1.6.8 for a while?  I noticed some ruby scripts are broken with ruby
1.8.0 and don't want to upgrade ruby to 1.8 on several machines.
Ruby-shim will not be maintained for long periodes, but still
it is useful for us to get smooth transition.

> 2) Older 1.6.8 packages will no longer be supported.

I disagree with this option because there will be a certain number of
people who stick to use 1.6.8 and they will want packages supporting
1.6.8 as well as 1.8.  Of course I am one of those ;-)

-- 
Mamoru KOMACHI <usata@gentoo.org>
http://dev.gentoo.org/~usata/

--
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] Ruby: depreciating 1.6.8 in favour of 1.8.0

[Aron Griffis]

[-- Attachment #1: Type: text/plain, Size: 731 bytes --]

Tom Payne wrote:	[Sun Aug 10 2003, 10:22:52AM EDT]
> I would like to update all of dev-ruby to use 1.8.0, and depreciate 1.6.8
> completely. Reasons for depreciating 1.6.8 are:

You mean "deprecate", I'm pretty sure.

I've seen a number of things break with 1.8.0 that worked on 1.6.8, even
in my own code.  It hasn't been hard to fix them, but it's taken some
time.

    # epm -ql ruby | grep -v 1.6  
    /usr/bin/ruby
    /usr/bin/irb
    /usr/lib/libruby.so
    /usr/share/man/man1/ruby.1.gz

Looks to me like it would be really easy to provide a SLOT="1.6" version
of the current ebuild, and make the new versions be SLOT="1.8".  Would
that be a good solution?  (Maybe not.. that's why I'm asking.)

Aron

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

[gentoo-dev] SLOT support for ruby

[Mamoru KOMACHI]

Hi all.

I added dev-lang/ruby-1.6.8-r2 and dev-lang/ruby-1.8.0-r1 (both
ebuilds are masked by package.mask) to support SLOT'd ruby. Some
ebuilds need to be rewritten to support both 1.6 and 1.8 (I'm working
on these ebuilds). If your ebuild works only on specific version of
ruby you need to refer to ruby as /usr/bin/ruby16 or /usr/bin/ruby18,
or inherit ruby eclass and set WANT_RUBY_1_6 or WANT_RUBY_1_8
respectively.

If you are interested in testing them, please unmerge previously
installed dev-lang/ruby first and emerge them (otherwise your ruby
will be overwritten). Feel free to test and file a bug report if you
find any bug ;)


Regards,

--
Mamoru KOMACHI <usata@gentoo.org>
http://dev.gentoo.org/~usata/


--
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] Ruby: depreciating 1.6.8 in favour of 1.8.0

[Mamoru KOMACHI]

Hi all,

At Sun, 12 Oct 2003 05:58:10 +0900,
I wrote:

> I added dev-lang/ruby-1.6.8-r2 and dev-lang/ruby-1.8.0-r1 (both
> ebuilds are masked by package.mask) to support SLOT'd ruby.

I unmasked ruby-1.6.8-r2 and ruby-1.8.0-r1. If you have installed
<=ruby-1.6.8-r1 or =ruby-1.8.0, please unmerge them first and upgrade
to ruby-1.6.8-r2 and/or ruby-1.8.0-r1.

At Sun, 10 Aug 2003 16:22:52 +0200,
Tom Payne wrote:

> I would like to update all of dev-ruby to use 1.8.0, and depreciate 1.6.8
> completely.

> Switching to 1.8.0 will also have downsides:
> 
> 1) Forcing 1.6.8 users to upgrade may break their code.
> 
> 2) Older 1.6.8 packages will no longer be supported.

Ruby 1.8.1 will be available in the near future (I just committed
ruby-1.8.1_pre2.ebuild) and I think it is the time to switch to
1.8. If users want ruby-1.6.8 along with 1.8.x they will be able to
use both 1.6.8 and 1.8.x (since they have different SLOT now). We will
concentrate on supporting packages for 1.8 from now on but keep 1.6.8
packages as well in case some packages may still be broken.

Any comments?


-- 
Mamoru KOMACHI <usata@gentoo.org>
http://www.gentoo.org/~usata/

--
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] Ruby: depreciating 1.6.8 in favour of 1.8.0

[Ferris McCormick]

On Sat, 1 Nov 2003, Mamoru KOMACHI wrote:

> Hi all,
> 
> At Sun, 12 Oct 2003 05:58:10 +0900,
> I wrote:
> 
> > I added dev-lang/ruby-1.6.8-r2 and dev-lang/ruby-1.8.0-r1 (both
> > ebuilds are masked by package.mask) to support SLOT'd ruby.
> 
> I unmasked ruby-1.6.8-r2 and ruby-1.8.0-r1. If you have installed
> <=ruby-1.6.8-r1 or =ruby-1.8.0, please unmerge them first and upgrade
> to ruby-1.6.8-r2 and/or ruby-1.8.0-r1.
>

.......

> 
> Ruby 1.8.1 will be available in the near future (I just committed
> ruby-1.8.1_pre2.ebuild) and I think it is the time to switch to
> 1.8. If users want ruby-1.6.8 along with 1.8.x they will be able to
> use both 1.6.8 and 1.8.x (since they have different SLOT now). We will
> concentrate on supporting packages for 1.8 from now on but keep 1.6.8
> packages as well in case some packages may still be broken.
> 
> Any comments?
> 
>

Sounds good to me.  I have been using ruby-1.8.0 on one of my (gentoo) 
sparc systems since late August with no problems.  My ruby use isn't
all that heavy, but it's enough > 0 that I was getting ready to send off
a query addressing this very subject, but you have preempted me.

As to 1.6.8 -vs- 1.8.x --- for me, at least, for some applications I am
forced into 1.8.0 because of the improved garbage collector performance.
(Along those lines, I'd like an easy way to set
 '-DGC_MALLOC_LIMIT=32000000' or some such in the CFLAGS for the build, 
rather than having to do it by hand, but that's another story....)

> -- 
> Mamoru KOMACHI <usata@gentoo.org>
> http://www.gentoo.org/~usata/
> 
> --
> gentoo-dev@gentoo.org mailing list
> 
> 
Regards,
--
Ferris McCormick (P44646, MI) <fmccor@inforead.com>
Phone: (703) 392-0303
Fax:   (703) 392-0401


--
gentoo-dev@gentoo.org mailing list