Bug 471246 – dev-lang/ruby-2.0.0_p195 version bump

• Status: RESOLVED FIXED
• Product: Gentoo Linux

[Description Ole Reifschneider (RETIRED) 2013-05-25 14:12:43 UTC]

I would love to be able to install ruby 2.0 with portage.

[Comment 1 Hans de Graaff 2013-05-26 08:09:32 UTC]

So would we, but unfortunately there are issues that currently prevent that. Off the top of my head (since multiple people have been working on this):

- ruby itself has an insecure RUNTIME path in socket.so
- rdoc 4.x fails tests
- rubygems 2.x fails tests
- rake 0.9.6 fails tests

All of these issues need to be resolved before we can add ruby 2.0 to the tree.

[Comment 2 Hans de Graaff 2013-06-03 19:32:28 UTC]

rdoc 4.0.1 is now in the tree.

[Comment 3 Hans de Graaff 2013-06-23 08:01:24 UTC]

rake 0.9.6 is now in the tree.

[Comment 4 Hans de Graaff 2013-06-23 09:50:19 UTC]

rubygems 2.0.3 is now also in the tree.

[Comment 5 Olipro 2013-06-28 19:24:54 UTC]

With the new ruby 2.0, apparently -D_FORTIFY_SOURCE=2 was added to the configure.in - does this in any way relate to resolving the insecure runtime path?

[Comment 6 Hans de Graaff 2013-06-29 06:44:17 UTC]

(In reply to Olipro from comment #5)
> With the new ruby 2.0, apparently -D_FORTIFY_SOURCE=2 was added to the
> configure.in - does this in any way relate to resolving the insecure runtime
> path?

I don't know. I've fixed the insecure runpath with the --disable-rpath, which should be safe for us since all ruby stuff will be installed in default ld locations.

Current holdback for 2.0 is with all the mandatory dependencies that we also need to install. We may not be able to fully unbundle everything in ruby20, at least for bootstrapping.

[Comment 7 Diego Elio Pettenò (RETIRED) 2013-06-29 15:58:29 UTC]

No, _FORTIFY_SOURCE has nothing to do with rpath whatsoever.

[Comment 8 Hans de Graaff 2013-07-07 08:16:20 UTC]

ruby-2.0.0_p247 is now in the tree.