Switch branches/tags
Nothing to show
Commits on Sep 5, 2010
Commits on Aug 31, 2010
Commits on Aug 5, 2010
Commits on Aug 4, 2010
  1. Avoid OpenSSL blow the build process due symlinks

    luislavena committed Aug 4, 2010
    OpenSSL contained symlinks which blows untar'ing
  2. Merge branch 'devkit'

    luislavena committed Aug 4, 2010
  3. Use basic-bsdtar instead of 7zip extraction.

    jonforums authored and luislavena committed Aug 4, 2010
    This wins on speed: there is no gz/bz2/lzma extraction and
    then untar.
  4. Disabled installer generation.

    jonforums authored and luislavena committed Aug 4, 2010
Commits on Jul 30, 2010
Commits on Jul 29, 2010
  1. Enhance dk.rb's RubyGems scanning algorithm.

    jonforums committed Jul 29, 2010
    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
Commits on Jul 28, 2010
  1. Enable Ruby core extensions and String#camelcase.

    jonforums committed Jul 28, 2010
    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
    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
    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
  2. Revert "Add bsdtar (libarchive 2.8.3)"

    luislavena committed Jul 28, 2010
    This reverts commit ea6cc50.
    See comments here for details of the revert:
Commits on Jul 27, 2010
  1. Whitespace cleanup

    luislavena committed Jul 27, 2010
Commits on Jul 26, 2010
  1. Update 1.9.2 config and use RubyGems GitHub repo.

    jonforums committed Jul 26, 2010
    Build ruby19 from ruby-1.9.2-rc2 rather than rc1 and use the RubyGems
    repo at instead of the repo at  Implement the corresponding
    changes in the rubygems recipe to use git rather than svn.
Commits on Jul 25, 2010
  1. Show new config override and DevKit SFX archive.

    jonforums committed Jul 25, 2010
    The DevKit can now be built as normal 7-Zip or self-extracting archives
    and the default build configuration can be overridden via a file in the
    root directory named override/build_config.rb.
  2. Allow default build configuration to be overridden.

    jonforums committed Jul 25, 2010
    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.
Commits on Jul 24, 2010
  1. Enhanced SFX packaging task.

    jonforums authored and luislavena committed Jul 24, 2010
    It now reuses the generated 7-zip package.
  2. Generate self extracting archive.

    jonforums authored and luislavena committed Jul 24, 2010