aboutsummaryrefslogtreecommitdiffstats
path: root/spec/bundler/install/gemfile
Commit message (Collapse)AuthorAgeFilesLines
* Prepare to release bundler-2.1.0Hiroshi SHIBATA2019-12-151-3/+3
|
* Merge Bundler 2.1.0.pre3 released versionHiroshi SHIBATA2019-11-132-6/+0
|
* Merge Bundler 2.1.0.pre.3Hiroshi SHIBATA2019-11-114-9/+9
| | | | | | | | | | | | | | | Features: - Add caller information to some deprecation messages to make them easier to fix [#7361](https://github.com/bundler/bundler/pull/7361) - Reconcile `bundle cache` vs `bundle package` everywhere. Now in docs, CLI help and everywhere else `bundle cache` is the preferred version and `bundle package` remains as an alias [#7389](https://github.com/bundler/bundler/pull/7389) - Display some basic `bundler` documentation together with ruby's RDoc based documentation [#7394](https://github.com/bundler/bundler/pull/7394) Bugfixes: - Fix typos deprecation message and upgrading docs [#7374](https://github.com/bundler/bundler/pull/7374) - Deprecation warnings about `taint` usage on ruby 2.7 [#7385](https://github.com/bundler/bundler/pull/7385) - Fix `--help` flag not correctly delegating to `man` when used with command aliases [#7388](https://github.com/bundler/bundler/pull/7388) - `bundle add` should cache newly added gems if an application cache exists [#7393](https://github.com/bundler/bundler/pull/7393) - Stop using an insecure folder as a "fallback home" when user home is not defined [#7416](https://github.com/bundler/bundler/pull/7416) - Fix `bundler/inline` warning about `Bundler.root` redefinition [#7417](https://github.com/bundler/bundler/pull/7417)
* [bundler/bundler] Revert "Add all platforms to lockfile by default"David Rodríguez2019-09-181-22/+4
| | | | | | This reverts commit 3dc509e645abb497e4dc92a7c42be471ff87db0b. https://github.com/bundler/bundler/commit/b5766564fb
* [bundler/bundler] Revert "Remove now meaningless warning"David Rodríguez2019-09-181-0/+19
| | | | | | This reverts commit 00b095b98fe4bd44950beaf3bc9f1d91eac7b69e. https://github.com/bundler/bundler/commit/e93bce3b20
* Fix some bundler specs (#2380)David Rodríguez2019-08-201-5/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * These seem to consistenly pass already * Show actual command when running `make test-bundler` Current the setup command that installs the necessary gems for testing bundler was printed, but not the actual command that runs the tests. That was a bit confusing. * Borrow trick from setproctitle specs * A title that long doesn't get set sometimes No idea why, but the test doesn't need that the title is that long. * Fix most gem helper spec ruby-core failures * Fix the rest of the gem helper failures * Fix version spec by improving the assertion * Remove unnecessary `BUNDLE_RUBY` environment var We can use `RUBY` when necessary, and `BUNDLE_RUBY` is not a good name because bundler considers `BUNDLE_*` variables as settings. * Rename `BUNDLE_GEM` to `GEM_COMMAND` This is more descriptive I think, and also friendlier for bundler because `BUNDLE_` env variables are interpreted by bundler as settings, and this is not a bundler setting. This fixes one bundler spec failure in config specs against ruby-core. * Fix quality spec when run in core Use the proper path helper. * Fix dummy lib builder to never load default gems If a dummy library is named as a default gem, when requiring the library from its executable, the default gem would be loaded when running from core, because in core all default gems share path with bundler, and thus they are always in the $LOAD_PATH. We fix the issue by loading lib relatively inside dummy lib executables. * More exact assertions Sometimes I have the problem that I do some "print debugging" inside specs, and suddently the spec passes. This happens when the assertion is too relaxed, and the things I print make it match, specially when they are simple strings like "1.0" than can be easily be part of gem paths that I print for debugging. I fix this by making a more exact assertion. * Detect the correct shebang when ENV["RUBY"] is set * Relax assertion So that the spec passes even if another paths containing "ext" are in the load path. This works to fix a ruby-core issue, but it's a better assertion in general. We just want to know that the extension path was added. * Use folder structure independent path helper It should fix this spec for ruby-core. * Fix the last failing spec on ruby-core * Skip `bundle open <default_gem>` spec when no default gems
* [bundler/bundler] Remove unnecessary rubygems monkeypatchDavid Rodríguez2019-08-181-1/+1
| | | | | | | Instead, make sure we always load the local copy of bundler during specs, and never end up using the default copy. https://github.com/bundler/bundler/commit/ac655ffeda
* [bundler/bundler] Fix inconsistent lockfile orderDavid Rodríguez2019-08-161-0/+44
| | | | | | | | When Gemfile would specify path sources as relative paths starting with "./", the lockfile would have inconsistent order on `bundle install` and `bundle update`. https://github.com/bundler/bundler/commit/c7532ced89
* [bundler/bundler] Indentation tweakDavid Rodríguez2019-08-161-6/+6
| | | | https://github.com/bundler/bundler/commit/5978a88f33
* [bundler/bundler] Always set `cache_all` via config during testsDavid Rodríguez2019-08-031-1/+2
| | | | | | | So that the behavior is the same regardless of the tested bundler version. https://github.com/bundler/bundler/commit/664549427a
* [bundler/bundler] Enable `Style/UnneededInterpolation` copDavid Rodríguez2019-08-031-2/+2
| | | | https://github.com/bundler/bundler/commit/4c6a3c3cf7
* [bundler/bundler] Remove now meaningless warningDavid Rodríguez2019-08-031-19/+0
| | | | https://github.com/bundler/bundler/commit/00b095b98f
* [bundler/bundler] Add all platforms to lockfile by defaultDavid Rodríguez2019-08-031-4/+22
| | | | https://github.com/bundler/bundler/commit/3dc509e645
* [bundler/bundler] Refactor some specsDavid Rodríguez2019-08-031-7/+7
| | | | https://github.com/bundler/bundler/commit/785c7af1f3
* [bundler/bundler] Make some specs more explicitDavid Rodríguez2019-08-031-13/+11
| | | | https://github.com/bundler/bundler/commit/5e08e849ec
* [bundler/bundler] Reuse `lockfile` spec helperDavid Rodríguez2019-08-031-4/+2
| | | | https://github.com/bundler/bundler/commit/e6a03f1102
* [bundler/bundler] Normalize file:// handling in specsDavid Rodríguez2019-08-0311-180/+180
| | | | https://github.com/bundler/bundler/commit/5946d62ad0
* Merge bundler master from upstream.Hiroshi SHIBATA2019-06-094-57/+80
| | | | Pick from 8dd59e3ba97eb80a599f8149f31bf40773b69dc0
* Skip to failing examples on ruby core repository.hsbt2019-04-141-2/+2
| | | | git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67541 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
* Merge Bundler 2.1.0.pre.1 as developed version from upstream.hsbt2019-04-149-220/+321
| | | | | | https://github.com/bundler/bundler/commit/a53709556b95a914e874b22ed2116a46b0528852 git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67539 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
* Merge Bundler 2.0.1 from upstream.hsbt2019-01-046-12/+12
| | | | git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66710 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
* Downgrade Bundler 1.17.x from 2.0.0.hsbt2018-12-116-12/+12
| | | | | | | | We have the platform issue on heroku: * https://gist.github.com/schneems/26452540f6e2bbbcf2ea144f45f6b305 * https://github.com/heroku/heroku-buildpack-ruby/issues/833 git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66323 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
* Merge upstream changes from 2-0-stable branch of bundler/bundler.hsbt2018-11-046-12/+12
| | | | | | * It update bundler 2 mode to bundler 3. git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@65523 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
* Added bundler as default gems. Revisit [Feature #12733]hsbt2018-11-0211-0/+4478
| | | | | | | | | | | * bin/*, lib/bundler/*, lib/bundler.rb, spec/bundler, man/*: Merge from latest stable branch of bundler/bundler repository and added workaround patches. I will backport them into upstream. * common.mk, defs/gmake.mk: Added `test-bundler` task for test suite of bundler. * tool/sync_default_gems.rb: Added sync task for bundler. git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@65509 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
* Postponing the Bundler merge.hsbt2017-12-2211-4316/+0
| | | | | | | I faced a big issue about Bundler with ruby core. I have no time to resolve it issue before 2.5 final release. git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@61416 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
* Merge release version of bundler-1.16.1 from upstream.hsbt2017-12-211-3/+2
| | | | git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@61388 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
* Follow up r60970 for bundler's examples.hsbt2017-12-072-17/+17
| | | | | | | r60970 break Gemfile.lock format with file protocol after bundle install/update. I addd hostname to these examples. git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@61071 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
* Update bundled bundler to 1.16.0.hsbt2017-11-0111-131/+541
| | | | | | | * lib/bundler, spec/bundler: Merge bundler-1.16.0. * common.mk: rspec examples of bundler-1.16.0 needs require option. git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@60603 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
* Merge bundler to standard libraries.hsbt2017-09-0810-0/+3907
rubygems 2.7.x depends bundler-1.15.x. This is preparation for rubygems and bundler migration. * lib/bundler.rb, lib/bundler/*: files of bundler-1.15.4 * spec/bundler/*: rspec examples of bundler-1.15.4. I applied patches. * https://github.com/bundler/bundler/pull/6007 * Exclude not working examples on ruby repository. * Fake ruby interpriter instead of installed ruby. * Makefile.in: Added test task named `test-bundler`. This task is only working macOS/linux yet. I'm going to support Windows environment later. * tool/sync_default_gems.rb: Added sync task for bundler. [Feature #12733][ruby-core:77172] git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@59779 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
generated by cgit v1.2.3 (git 2.39.1) at 2024-07-22 09:49:38 +0000