Is the ruby 1.8.7 update incompatible with 1.8.6?

[Stanislav Sedov]

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

On Thu, 12 Feb 2009 16:30:03 +0000 (UTC)
Stef <stef-list at memberwebs.com> mentioned:

> The PR about updating ruby18 to 1.8.7 says that the update breaks rails.
> It was noted "We're not going to update to 1.8.7-p17" and then 3 days
> later the commit upgrading to p72 took place.
> 
> http://www.freebsd.org/cgi/query-pr.cgi?pr=124837
> 
> Is there a part of the discussion I'm missing? Is p72 guaranteed
> compatible with 1.8.6? The release website doesn't say anything interesting:
> 
> http://www.ruby-lang.org/en/news/2008/08/11/ruby-1-8-7-p72-and-1-8-6-p287-released/
> 
> 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.

Let me know if there're any problems with update.

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

iEYEARECAAYFAkmUVXkACgkQK/VZk+smlYE5uQCggJxUsVxKs2JQf5qieUxuQM3K
dgMAn0pRqCaMrnvFSVQuvCEtBLS1F/Fa
=JvES
-----END PGP SIGNATURE-----

!DSPAM:49945561967001291497471!