DevKit's dk.rb setup helper script now searches for RubyGems in both site_ruby and core Ruby locations, preferring site_ruby installs over core Ruby installs when proving RubyGems override script. The fallback is to inject batch stubs into the Ruby 'bin' directory if RubyGems is not found in either of site_ruby or core Ruby locations. DevKit enhancement summary: 1) site_ruby/**/rubygems -> inject defaults/operating_system.rb 2) lib/ruby/**/rubygems -> inject defaults/operating_system.rb 3) inject batch stubs into <RUBY_INSTALL_DIR>/bin
Extensions to the Ruby core classes live in the rake/core_ext directory and are enabled by updating rake/core_extensions.rb to require them. The actual extension consists of two parts, both in the rake/core_ext directory. Part One is a file named after the Ruby core class that you intend to extend, for example rake/core_ext/string.rb. It's responsibility is to require all files implementing extensions to a particular core Ruby class. Part Two is a subdirectory named after the Ruby core class you're extending. For example, rake/core_ext/string/. This subdirectory holds all the files that actually extend the core class named by the subdirectory. Use multiple files to liberally modularize your extension code. Finally, bringing everything together for use by the project rakefile, the rake/core_extensions.rb file requires all Ruby core extensions you've provided in Part One and Two. Confusing? Don't let the above wording slow you down one bit. Check out the code for the String#camelcase extension as managed by the following files: * rakefile.rb * rake/core_extensions.rb * rake/core_ext/string.rb * rake/core_ext/string/conversions.rb
This reverts commit ea6cc50. See comments here for details of the revert: http://github.com/oneclick/rubyinstaller/commit/ea6cc50449c591a99e37ca83af3bb160155eb6b7
Provide an override/build_config.rb file in the root of the project to override the default build configuration contained in the files in the config/ directory.