Skip to content

Commit

Permalink
Mention #596 in History
Browse files Browse the repository at this point in the history 
This does not mean work for this issue is complete, at the present time
the following items are missing:

Behavior when the destination directory is not writable (exception or
build into ~/.gem).

Behavior for static vs shared ruby.
  • Loading branch information
@drbrain
drbrain committed Oct 7, 2013
1 parent 908953e commit 3a924d3
Showing 1 changed file with 4 additions and 0 deletions.
4 changes: 4 additions & 0 deletions History.txt
View file
Original file line number Diff line number Diff line change
Expand Up @@ -30,6 +30,10 @@ Minor enhancements:
Gem::Ext::BuildError. The old constant is an alias for the new constant.
* When extensions are built the gem_make.out file is always written now, even
on success. This will help with debugging bad builds that report success.
* A RubyGems directory may now be shared amongst multiple ruby versions. Upon
activation RubyGems will automatically compile missing extensions for the
current platform when the built objects are missing. Issue #596 by Michal
Papis

=== 2.1.4 / 2013-09-17

Expand Down

2 comments on commit 3a924d3

@rdp
Copy link

@rdp rdp commented on 3a924d3 Oct 8, 2013

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

how does it know what the built objects are?

@drbrain
Copy link
Member Author

@drbrain drbrain commented on 3a924d3 Oct 8, 2013

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Previously the extensions were installed in $GEM_HOME/gems/my_gem-1.0/lib, now they are installed in $GEM_HOME/extensions/my_gem-1.0/ruby_api_version/ruby_platform/. If the directory does not exist the extension must be built.

Also, there is a .gem.build_complete file created in the directory in case the build failed. If the file is missing the extension must be built. See prior commits for details

Please sign in to comment.