Is the ruby 1.8.7 update incompatible with 1.8.6?

[Stanislav Sedov]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Fri, 13 Feb 2009 02:27:11 +0000 (UTC)
Stef <stef-list at memberwebs.com> mentioned:

> Stanislav Sedov wrote:
> > On Thu, 12 Feb 2009 16:30:03 +0000 (UTC)
> > Stef <stef-list at memberwebs.com> mentioned:
> >> Devs of the systems I maintain are saying that they can't use 1.8.7 due
> >> to incompatibilities with rails and other breakages, and now suddenly
> >> there's no version of 1.8.6 in ports.
> > 
> >> I'm not ruby guy myself, but I do try to support it as best I can.
> >> Ruby's irresponsible versioning and breakage of their software makes my
> >> job painful, and I'm slowly developing a grudge against ruby :/
> > 
> >> However I've been very thankful for the modicum of sanity that FreeBSD
> >> ports brought to ruby versions. Is that now gone too? Tell me it isn't so.
> > 
> > This version is belived to be fully compatible with ruby-1.8.6 line. At least,
> > it fully passes the rubyspec tests (http://www.rubyspec.org/, also see
> > "validate" target in Makefile), so there should be no problems.
> > 
> > The main concern with ruby-1.8.7 was it's incompatibility with rails, and
> > some stability problems. All of them was resolved. Today, 1.8.7 is recommended
> > for rails, as noted on their site.
> 
> That's great news. I'll work on building packages for devs to deploy to
> their test systems.
> 

Yeah, but anyway it requires a testing first before deployment, epsecially if
rails used as they tend to dig deeply into all dirty corners of the language.

My rails 2.2.2 survived the update, but I can't say anything about other versions.

So be careful (but you probably already know that)!

- -- 
Stanislav Sedov
ST4096-RIPE
-----BEGIN PGP SIGNATURE-----

iEYEARECAAYFAkmVHvIACgkQK/VZk+smlYHB7ACfYL748rGUi1GVe8RbStr6lGfJ
JV0An2Gugk0O+nGP06cdTJS05N4NyEy9
=0YHz
-----END PGP SIGNATURE-----

!DSPAM:49951ed8967006981484228!