| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
This will avoid printing out every single cached spec
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
closes #3850
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
Version 1.9.4
Conflicts:
lib/bundler/installer.rb
lib/bundler/match_platform.rb
lib/bundler/source/rubygems.rb
|
| |
|
|
|
|
| |
This reverts commit 9263e08636d25e2573776b17416e6fabd403026b.
|
|
|
|
|
|
|
| |
This class (and only this class) knows about gems that are installed
locally or present in vendor/cache. Because we now have multiple source
objects, it's much more efficient to only load the installed and cached
specs into one of those sources rather than all Rubygems sources.
|
|
|
|
|
|
|
|
|
|
|
|
| |
We're pulling out svn source support into a plugin. While we work on
that, you can use the 1.8.0.svn release, but subversion sources aren't
an official part of Bundler itself.
This reverts commit 049d281d0fdcc29297a21c6a66cd7efc38690675.
This reverts commit 22fecdd07fdf02edb1a8824fb73dd7e015507644.
This reverts commit 38f195e11f37ce5139af4ff3384eb2f26c2edb19.
This reverts commit 500436a33de0b884525dbf82cfc69332fc96f8b9.
This reverts commit 2c356be90a23921058cd14fd0e4a366da195021a.
|
| |
|
|\
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Version 1.7.1
Conflicts:
CHANGELOG.md
lib/bundler/dsl.rb
lib/bundler/index.rb
lib/bundler/lockfile_parser.rb
lib/bundler/source/rubygems.rb
man/gemfile.5.ronn
|
| | |
|
| |
| |
| |
| | |
with @TimMoore and @ckrailo
|
|/ |
|
|\
| |
| |
| |
| |
| |
| |
| |
| | |
Displays the previous version of the gem when run bundle update
Conflicts:
lib/bundler/source.rb
lib/bundler/source/git/git_proxy.rb
lib/bundler/source/rubygems.rb
|
| |
| |
| |
| |
| |
| |
| | |
Change bundle update message format
Change rspec bundle update message text to match in files (rubygem, git, path
source, etc)
|
| |
| |
| |
| |
| |
| |
| |
| | |
Change code in the 3 source files to display the method locked_gems in
lib/bundler.rb
Add 3 Rspec test in the update directory for each source: rubygems, git,
path.
|
| | |
|
|/ |
|
| |
|
| |
|
|
|
|
|
|
|
| |
From this commit on, we add a .bundlecache file inside
each git/path directory in vendor/cache so we know it
came from bundler. This allow us to delete those specific
directories without messing with user's specific ones.
|
|
|
|
| |
closes #1989
|
| |
|
| |
|
|\
| |
| |
| |
| |
| | |
Conflicts:
lib/bundler/source.rb
spec/install/git_spec.rb
|
| | |
|
| | |
|
| | |
|
|/ |
|
|\
| |
| |
| |
| |
| |
| |
| | |
Conflicts:
CHANGELOG.md
lib/bundler/version.rb
1.1.3 release merge
|
| | |
|
| |
| |
| |
| |
| | |
This reverts commit d6f93f82bff9ca09c5b7b46d15c1c07154c9233e, reversing
changes made to f65ba393f43bb697e655645e61e2ca52fc05e28e.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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.
|
|/ |
|