Ruby 1.9.0-4 is released

Hi,

Ruby 1.9.0-4 has just been released. This is a snapshot release.

The next release is 1.9.0-4. It will be released at 25 Sep. See
[ruby-core:17644] for more details.

== Location
You can fetch it from:

ftp://ftp.ruby-lang.org/pub/ruby/ruby-1.9.0-4.tar.bz2
MD5=429cf38c075332118860f58152291954
SHA256=09a91a60fba308a45ab8d3e691ec5ab279b36b646e75ad68d1d45679bdc4cbce
SIZE=5546544

ftp://ftp.ruby-lang.org/pub/ruby/ruby-1.9.0-4.tar.gz
MD5=12836c96133f6a656bfe9159477a4575
SHA256=99a1d460fe0b5b3ba1e2465f3744aea6b1176b2803222a0e7113f4dde8bc8ff8
SIZE=6699896

ftp://ftp.ruby-lang.org/pub/ruby/ruby-1.9.0-4.zip
MD5=06ae8573bcab645741c03dc63fbb8193
SHA256=6116d479820a836e3304db1d09131de2840aca7341d50e2d31da02cf13e15a53
SIZE=7889585

== News

  • transcode
    Encoding::Converter: new class

  • Universal newline

    • open(“path/to/file”, “rt”) converts LF, CR, CRLF to LF.

    • open(“path/to/file”, “rb”) does not.

    • open(“path/to/file”, “r”) is equivalent to “rt” or “rb”.
      It depend on the evironment.

    • “wt” and “w” conert LF to LF or CRLF. The converted character
      depends on the environment.

    • “wb” does not convert.

== Maintainers are wanted
The following platforms was supported once by Ruby but now Ruby has no
active maintainer for them. Perhaps Ruby 1.9.0-4 does not work on them.

  • BeOS
  • WinCE
  • OS/2
  • bcc32
  • Classic MacOS
  • VMS
  • djgpp
  • human68k

I will remove platform-specific codes for WinCE, OS/2, bcc32, Classic
MacOS, VMS, djgpp, and human68k from Ruby, unless someone
become a maintainer for it by 25 Sep.

see [ruby-talk:311117] for more details.

Regards,

On Monday 25 August 2008 12:03:31 Yugui (Yuki S.) wrote:

Hi,

Ruby 1.9.0-4 has just been released. This is a snapshot release.

The next release is 1.9.0-4.

Probably 1.9.0-5? Or you could just release this one again…

Thanks, though – compiling now.

Ruby 1.9.0-4 instantly broke Hpricot. Reinstalling from the gem fixed
it.

Now, this shouldn’t happen, but I’m compiling the development version of
Ruby
from source, so I should be expecting issues like this.

But for that particular problem, is there a way to automagically rebuild
all
gems? Or at least those with native extensions – I’d guess those would
be
the first to break.

On Tuesday 26 August 2008 23:33:39 Tim P. wrote:

You would need to write a script that dumps a list of your gems with
native extensions (look for .so or .bundle files), upgrade ruby, then
run the script again to reinstall the native gems.

In which case, probably easier to just reinstall all of them.

On Aug 26, 2008, at 10:14 PM, David M. wrote:

would be
the first to break.

You would need to write a script that dumps a list of your gems with
native extensions (look for .so or .bundle files), upgrade ruby, then
run the script again to reinstall the native gems.

Hey, new ruby quiz!

Blessings,
TwP

This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.

| Privacy Policy | Terms of Service | Remote Ruby Jobs