Bug #995

CONFIG['topdir'] defined '1.9.1' instead of '1.9'

Added by Luis Lavena about 3 years ago. Updated 10 months ago.

[ruby-core:21236]
Status:Rejected Start date:01/09/2009
Priority:Normal Due date:
Assignee:- % Done:

0%
Category:core
Target version:1.9.1 RC2
ruby -v:

Description

While working on the new One-Click installer, noticed this change the
the folder structure between 1.8 and 1.9.1

On 1.8, RbConfig::CONFIG['topdir'] defines MAYOR dot MINOR as
part of the folder structure for libraries and such
(lib/ruby/1.8/i386-mingw32)

While 1.9.1 set the version and the directory to MAYOR.MINOR and
TEENY, affecting the folder structure where rbconfig is located:
/lib/ruby/1.9.1/i386-mingw32)

This is important for me since I need to strip build path from the
file to allow portability to other computer locations.

I see that future 1.9.2 or 1.9.4 versions will break many setups,
making upgrade from versions a bit complicated.

Is the change intentional?

History

#1
Updated by Yuki Sonoda about 3 years ago

  • Status changed from Open to Rejected
This is intentional. CONFIG['topdir'] will change  when binary compatibility is broken in a future version.

#2
Updated by Luis Lavena about 3 years ago

Thank you for your reply.

This will require me keep a separate recipe for building 1.9 in a different way than 1.8, due this change of file location.

There is a place in the documentation or previous discussion I can link users to check?

Also available in: Atom PDF