Skip to content
Commits on Dec 4, 2013
  1. @evanphx

    .span, not .new

    evanphx committed Dec 3, 2013
  2. @evanphx
  3. @evanphx
Commits on Dec 3, 2013
  1. @evanphx
  2. @evanphx

    Add missing file

    evanphx committed Dec 3, 2013
  3. @evanphx
  4. @evanphx

    Merge branch 'fix-dep-res'

    Conflicts:
    	lib/rubygems/resolver/requirement_list.rb
    evanphx committed Dec 3, 2013
  5. @evanphx
  6. @evanphx

    Speed up resolution by considering exact reqs first

    Exact requirements keep the tree constraint and thus speed things up by
    restricting the ammount of backtracking that is available.
    evanphx committed Dec 3, 2013
  7. @evanphx
Commits on Dec 1, 2013
  1. @drbrain

    Copy extension directories into lib too

    This correctly fixes [ruby-trunk - #9106].  The initial fix did not copy
    directories properly so an extension installed by RubyGems 2.2 would not
    work correctly on RubyGems 2.1, nor would gems that don't trust
    $LOAD_PATH work correctly.
    drbrain committed Dec 1, 2013
Commits on Nov 30, 2013
  1. @drbrain

    Add #723, #725 to History

    drbrain committed Nov 30, 2013
  2. @amatsuda @drbrain
  3. @drbrain

    Write lock file when installing from gem.deps.rb

    This roughly matches what I think bundler behavior is.  I didn't go back
    and read the tests, so I hope it is right.
    drbrain committed Nov 30, 2013
  4. @drbrain

    Add RequestSet::Lockfile#write

    This allows a lock file to be written alongside the gem.deps.rb (or
    other) dependency file.
    
    This overwrites the existing file regardless of an existing file which
    may be incorrect behavior.
    drbrain committed Nov 30, 2013
  5. @drbrain

    Use the .lock file to install gem dependencies

    Now a .lock file will be used if present when installing gem
    dependencies.  This is designed to ensure the same gem versions are used
    across multiple installs.
    
    I'm not sure if RubyGems' resolver architecture behaves identically to
    bundler.  RubyGems doesn't presently run bundler's integration tests, so
    compatibility is not known.
    drbrain committed Nov 30, 2013
  6. @drbrain
  7. @drbrain

    Ignore missing .lock files for gem dependencies

    This makes use of the lock file transparent.
    drbrain committed Nov 30, 2013
  8. @drbrain
  9. @drbrain

    Add Source::Lock#==

    The superclass Source#== issues a warning when called, so restore
    Comparable#<=>'s behavior.
    drbrain committed Nov 30, 2013
  10. @drbrain

    Add Source::Lock#fetch_spec

    This delegates to the wrapped spec so it can act as a stand-in for the
    real source.
    drbrain committed Nov 30, 2013
  11. @drbrain

    Add Gem::Source::Lock

    The lock source wraps the original source and sorts before un-locked
    sources.
    drbrain committed Nov 30, 2013
Commits on Nov 29, 2013
  1. @drbrain

    Merge pull request #723 from amatsuda/alreaby

    s/alreaby/already/
    drbrain committed Nov 29, 2013
  2. @amatsuda

    s/alreaby/already/

    amatsuda committed Nov 29, 2013
Commits on Nov 27, 2013
  1. @drbrain

    Add IndexSet#pretty_print

    drbrain committed Nov 27, 2013
  2. @drbrain

    Fix pretty_print for empty VendorSet and GitSet

    If break is used the closing ] is not printed.  next allows it to print.
    drbrain committed Nov 27, 2013
  3. @drbrain

    Add BestSet#pretty_print

    drbrain committed Nov 27, 2013
  4. @drbrain

    Add VendorSet#pretty_print

    drbrain committed Nov 27, 2013
  5. @drbrain

    Add LockSet#pretty_print

    drbrain committed Nov 27, 2013
  6. @drbrain

    Add GitSet#pretty_print

    drbrain committed Nov 27, 2013
  7. @drbrain

    Add pretty_print for FakeFetcher

    drbrain committed Nov 27, 2013
  8. @drbrain

    Ignore default gems when validating

    You can't install, uninstall or repair default gems.  They sometimes
    lie.  Don't bother checking them for alien files.
    drbrain committed Nov 26, 2013
  9. @drbrain

    Resolve spec source file when setting loaded_from

    When uninstalling a gem the specification's directory and GEM_HOME are
    compared to make sure the gem comes from the installation directory.  If
    these don't match the gem is not installed.
    
    When the specification's file name is not fully expanded it will not
    match GEM_HOME (which is) so rubygems will incorrectly refuse to
    uninstall the gem.
    
    Now the directory is expanded.
    
    Fixes #708
    drbrain committed Nov 26, 2013
  10. @drbrain

    Fix installation of git: gems

    This introduces a functional test for Gem::Ext::Builder which ensures
    that the builder looks for the extension source in the correct place.
    drbrain committed Nov 26, 2013
  11. @drbrain

    Allow extension_install_dir to be changed

    This also caches extension_install_dir.
    drbrain committed Nov 26, 2013
Something went wrong with that request. Please try again.