summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* puts debugging, woowtf_travisAndre Arko2015-01-261-0/+7
|
* build on travisAndre Arko2015-01-261-96/+1
|
* warn or error on multiple primary sourcesAndre Arko2015-01-264-2/+36
|
* Version 1.8.0.pre with changelogv1.8.0.preAndre Arko2015-01-262-4/+22
|
* Revert "Handle s3 source"Andre Arko2015-01-256-90/+0
| | | | | | | | | | | | | | | | | | | | | | | | Unfortunately, AWS S3 credentials may contain characters that are not valid in a URI. That means that the credentials cannot be provided in the URI "basic auth" format, which is the only format Bundler currently supports. As a result, it seems that this feature is broken both in Rubygems and here in Bundler. Attempts to fix the problem[1] have stalled out, and no one on the Bundler core team uses S3 sources, so we've decided to not release support for S3 sources as part of the Bundler gem itself. We're working on a plugin system that will allow S3 support to be implemented and updated without requiring new versions of Bundler to be released. In the meantime, if this support is very important to allow you to continue to work, you can use the the 1.8.0.svn gem as a workaround. [1]: https://github.com/bundler/bundler/pull/3345 This reverts commit 1ded21eee6bd5d20a767f0b0e1a332d268788de2. This reverts commit b98338344f0a2e33905aa7c4a573a289bf7de06f. This reverts commit 26214a3fec5421c23888c8f65932af45b288a54b. This reverts commit ec0ef95ac8444a4221ab0469ad9200e0eafa37e4.
* Revert "svn source support"Andre Arko2015-01-2525-1550/+19
| | | | | | | | | | | | 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.
* reword clean system gems warningAndre Arko2015-01-251-1/+2
|
* omg banner is not desc, this is way betterAndre Arko2015-01-251-11/+11
| | | | | old: -t [--test=set the test framework] new: -t [--test] # set the test framework
* do not return global .bundle as local .bundleAndre Arko2015-01-251-3/+9
|
* move gem bins to exe/ and add console and setupAndre Arko2015-01-257-10/+40
|
* clean up and reword a bit asking about gem filesAndre Arko2015-01-253-18/+35
|
* Extended gem generation and generation settingsKir Shatrov2015-01-257-24/+149
| | | | | | | | | | | | | As discussed in https://github.com/bundler/bundler/pull/3305#issuecomment-67024669, the gem generator should not generate default files that change the rights or responsibilities of gem authors without their explicit consent. Let's change the gem generator to ask gem authors what they want, and allow them to change it via config or --flags. * Remove LICENSE from default gem * Remove CODE_OF_CONDUCT from default gem * Add --coc flag to generate CODE_OF_CONDUCT * Add --mit flag to generate LICENSE * On gem generation, if not set to true/false, ask user if they are willing to license their code permissively under the MIT license * On gem generation, if not set to true/false, ask user if they are willing to add a Code of Conduct to their gem * On gem generation, if not set to false/rspec/minitest, ask if the user would like to generate tests along with their gems. Save the answer as bundle config gem.tests. * Ensure that --coc, --mit, --test flags overrule any config settings that may be set.
* allow cache path to be configuredAndre Arko2015-01-258-22/+61
| | | | | | | this adds `package —cache-path`, supports `config cache_path foo`, and honors the BUNDLE_CACHE_PATH environment variable. closes #3351
* Revert .consolerc (sorry, @andremediros :grimace:)Andre Arko2015-01-257-19/+0
| | | | | | | | | Rather than adding .consolerc and seeing the surface area of things that Bundler supports continue to grow endlessly, Bundler 2.0 will deprecate the `bundle console` command, and instead add a script to each generated gem that loads `bundler/setup` and then loads the gem. Anyone can then edit that file to run the REPL they want, load the fixtures they want, and everything else, without anything specific to Bundler at all.
* credit benlakeyAndre Arko2015-01-251-1/+2
|
* test 1-8-stable on travisAndre Arko2015-01-251-0/+1
|
* test AnonymizableURI auth parameterAndre Arko2015-01-252-7/+19
|
* refactor to allow host-based config auth, tooAndre Arko2015-01-252-23/+29
| | | | | | | | we were previously forcing the configured auth if any was set, and it was only by a quirk of the URI not matching if it had user and pass set that we didn’t overwrite the Gemfile userinfo. Now that we also check for hostname-level configured userinfo, we have to detect whether the original URL in the Gemfile has userinfo and preserve it if it exists.
* repair issues merging v1.7.12Andre Arko2015-01-241-18/+9
|
* Merge tag 'v1.7.12'Andre Arko2015-01-249-55/+136
|\ | | | | | | | | | | | | | | | | Version 1.7.12 Conflicts: CHANGELOG.md lib/bundler/fetcher.rb spec/cache/platform_spec.rb
| * Revert "use gemfile over settings (not tested yet)"v1.7.12Andre Arko2015-01-121-3/+1
| | | | | | | | | | | | | | | | | | It turns out that we already use Gemfile auth over configured auth, because the Gemfile URI includes the username and password. That means that mirrors and configured auth will not be used for any URI with auth in it. This reverts commit 88969b5210cbab4226cdcc4245762f8c3ba41f1a.
| * use gemfile over settings (not tested yet)Andre Arko2015-01-091-1/+3
| |
| * Version 1.7.12 with changelogAndre Arko2015-01-082-1/+7
| |
| * Merge pull request #3342 from TimMoore/issue-3297-always-use-source-credentialsAndré Arko2015-01-083-41/+60
| |\ | | | | | | Always use source credentials
| | * Always use configured source credentials.Tim Moore2015-01-081-41/+38
| | | | | | | | | | | | | | | | | | | | | | | | | | | Previously, it tried to make anonymous requests, then retried with credentials if it got a 401 or 403. This caused issues with many private gem servers. Fixes #3297, #3296, #3180.
| | * Failing spec for 403 responses.Tim Moore2015-01-082-0/+22
| |/
| * Revert "Merge pull request #3262 from arronmabrey/use_api_auth-1-7-stable"Tim Moore2015-01-081-1/+1
| | | | | | | | | | This reverts commit 5d5651d35bbda4ad526c8f86bb2ce03f501a9eae, reversing changes made to 714f23e99c9628260909e11099dcfba3dda35b0a.
| * Version 1.7.11 with changelogv1.7.11Andre Arko2015-01-042-1/+7
| |
| * Merge pull request #3328 from myabc/ruby-22-fixesAndré Arko2014-12-302-1/+10
| |\ | | | | | | Ruby 2.2: support mri_22, (x64_)mingw_22 as platform options
| | * Teach Bundler to recognize (x64_)mingw_22 platformAlex Coles2014-12-302-1/+7
| | | | | | | | | | | | | | | | | | See e6bc48eb. Signed-off-by: Alex Coles <alex@alexbcoles.com>
| | * Teach Bundler to recognize mri_22 platformAlex Coles2014-12-302-0/+3
| |/ | | | | | | | | | | See e6bc48eb. Signed-off-by: Alex Coles <alex@alexbcoles.com>
| * Version 1.7.10 with changelogv1.7.10Andre Arko2014-12-292-1/+11
| |
| * his github username is TimMoore, it turns outAndre Arko2014-12-291-8/+8
| |
| * Revert "Don't change i18n version of Ruby 1.8 spec"Tim Moore2014-12-221-1/+1
| | | | | | | | This reverts commit 7f940849bd0e3ffb1a48433b5d058e51b0d3ae0f.
| * Pin i18n to 0.6.x in parallel specs.Tim Moore2014-12-221-0/+2
| | | | | | | | This should fix the build on Ruby 1.8.7.
| * Don't change i18n version of Ruby 1.8 specSmit Shah2014-12-221-1/+1
| |
| * Fixed a broken i18n specSmit Shah2014-12-221-2/+2
| |
| * Merge pull request #3309 from thomasfedb/ruby_22André Arko2014-12-144-2/+65
| |\ | | | | | | Added ruby_22? and friends to CurrentRuby.
| | * Added ruby_22? and friends to CurrentRuby.Thomas Drake-Brockman2014-12-144-2/+65
| |/
| * Merge pull request #3301 from TimMoore/issue-3298-unlocked-sourcesAndré Arko2014-12-112-2/+34
| |\ | | | | | | Convert sources to lock format before comparing.
| | * Convert sources to lock format before comparing.Tim Moore2014-12-112-2/+34
| |/ | | | | | | | | | | | | If the Gemfile sources lock to the same result as the current locked sources, they haven't changed. Closes #3298.
* | expand the multiple-source warningAndre Arko2015-01-231-0/+1
| | | | | | | | [ci skip]
* | Merge pull request #3358 from tdtds/patch-1André Arko2015-01-231-1/+1
|\ \ | | | | | | untaint gem path loaded from github
| * | untaint gem path loaded from githubTADA Tadashi2015-01-221-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | require fails because security error, in condition of: * $SAFE is 1 * gems from git or github. ex: gem 'bar', :github => 'foo/bar' original full_gem_path method in rubygems is untaint all paths of gems (in find_full_gem_path method), but Bundler override the method without untaint.
* | | remove obsolete support linksAndre Arko2015-01-221-6/+0
|/ /
* | ensure exitstatus while testing Bundler.setupAndre Arko2015-01-211-52/+20
| |
* | optional exit checkAndre Arko2015-01-211-17/+14
| | | | | | | | turns out Bundler.setup by itself won’t actually set the exitstatus unless it’s also running inside a TTY (which this isn’t).
* | clean up some missed some @exitstatusAndre Arko2015-01-205-16/+16
| |
* | don’t test exitstatus when it is unknownAndre Arko2015-01-2021-69/+69
| | | | | | | | | | | | apparently on some Ruby 1.8.7 installs, open3 doesn’t return an exit status, and that includes all Travis installs of 1.8.7. :/ these tests all pass (while checking exit status) on my machine, but they shouldn’t fail if the Ruby on Travis isn’t able to provide exitstatuses.
* | this test works in real life :(Andre Arko2015-01-201-12/+12
| | | | | | | | | | I cannot figure out how to get it to pass with the new, faster exec, but it passes in real life when I run the same command with (I think) the same environment variables. Arrrrgh.
View Lorry Controller Status