Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP
Commits on Mar 26, 2012
  1. Merge pull request #1796 from Fluxx/add_docs_for_no_cache

    André Arko authored
    Add docs for the --no-cache option
  2. @Fluxx
Commits on Mar 24, 2012
  1. @hone

    Merge branch '1-1-stable'

    hone authored
    Conflicts:
    	CHANGELOG.md
    	lib/bundler/version.rb
    
    1.1.3 release merge
  2. @hone

    Bundler 1.1.3

    hone authored
  3. @hone

    update changelog for 1.1.3

    hone authored
  4. @indirect

    Revert "Merge pull request #1789 from tenderlove/pathescape"

    indirect authored
    This reverts commit d6f93f8, reversing
    changes made to f65ba39.
Commits on Mar 23, 2012
  1. @tenderlove @hone

    bundler root path should be escaped

    tenderlove authored hone committed
  2. @hone
  3. @hone
  4. @sferik

    Merge pull request #1789 from tenderlove/pathescape

    sferik authored
    bundler root path should be escaped
  5. @tenderlove
Commits on Mar 22, 2012
  1. @josevalim
  2. @josevalim
  3. @josevalim
  4. @josevalim
Commits on Mar 21, 2012
  1. @hone

    Revert "Add simple cache to Bundler.load_gemspec"

    hone authored
    This reverts commit 3d4163a.
    
    Breaks the build. I'm reverting this for now, until we can take a look
    into why this breaks it.
  2. @hone

    Merge branch '1-1-stable'

    hone authored
    Conflicts:
    	CHANGELOG.md
    	lib/bundler/version.rb
    
    1.1.2 release merge
  3. @hone

    Bundler 1.1.2

    hone authored
  4. @hone

    update changelog for 1.1.2

    hone authored
  5. @hone

    Fixes #1782. Don't remove duplicate PATH sources

    hone authored
    When using specifying version number, you can have multiple PATH
    sections for the same source.
    
    We were over eager in
    bundler@e31a1c7#L1R51.
    We should only remove the duplicate GIT sources, so let's explicitly
    check for that.
  6. @hone

    Test case for bundle install not checking out git

    hone authored
    During the 1.1 pre/RC releases, there were duplicate GIT source sections
    generated in the `Gemfile.lock`. These would confuse bundler and the
    wrong source would get attached to the spec. This test case breaks if we
    don't fix this here:
    bundler@e31a1c7#L1R51
Commits on Mar 20, 2012
  1. @josevalim
  2. @josevalim
  3. @josevalim
  4. @josevalim
  5. @josevalim
Commits on Mar 19, 2012
  1. @josevalim

    Update CHANGELOG.md

    josevalim authored
  2. @josevalim

    Ensure tests pass on 1.8.7.

    josevalim authored
  3. @josevalim
  4. @josevalim
  5. @josevalim

    Do not resolve if the local override did not change.

    josevalim authored lolwut committed
  6. @josevalim

    Initial implementation of local git repos.

    josevalim authored lolwut committed
    The proposal of this patch is to implement a functionality
    that allow developers to work against a git repository locally.
    
    This can be achieved by setting up a local override:
    
        bundle config rack.local ~/path/to/local/rack
    
    Now, instead of checking out a git repository, the local override
    will be used. This implies a few things:
    
    Similar to path, every time the local git repository change,
    changes will be automatically picked up by Bundler; This means a
    commit in the local git repo will update the revision in the
    Gemfile.lock to the local git repo revision. This requires the
    same attention as git submodules. Before pushing to remote,
    you need to ensure the local override was pushed, otherwise you
    may point to a commit that only exists in your local machine.
    
    Also, we are doing many checks to ensure a developer won't work
    with invalid references. Particularly, we force a developer to
    specify a branch in the Gemfile in order to use local overrides
    and, if your local repository is on another branch, we will abort.
    This allows a developer to change between topic or release branches
    without accidentally changing the reference in the Gemfile.lock.
    
    We also ensure that the current revision in the Gemfile.lock exists
    in the current local override. By doing this, we force the local
    override to fetch the latest changes in the remotes.
    
    There are a few things missing before this change can be merged in:
    
    1) We could improve `bundle check` to validate the conditions above.
       With this in mind, a developer could add a pre-commit hook that
       invokes `bundle check` to ensure he isn't pushing an old or invalid
       reference. However, it will be up to the developer to ensure his
       local overrides are not dirty or that they were pushed to remote.
    
    2) Currently, every time there is a local override, we are automatically
       by passing locked specs, regardless if there was a change or not.
       We need to improve this scenario in order to improve performance.
    
    3) `bundle config foo bar` sets the configuration value for the
       current user (~). We need to be able to set project configuration
       and delete them as well.
  7. @josevalim

    Encapsulate git source interaction in a git proxy.

    josevalim authored lolwut committed
  8. @josevalim

    Refactor a couple methods in Bundler.definition

    josevalim authored lolwut committed
Commits on Mar 18, 2012
  1. @rohit

    Add CI status image in README

    rohit authored
Something went wrong with that request. Please try again.