summaryrefslogtreecommitdiff
path: root/lib/bundler/dsl.rb
Commit message (Collapse)AuthorAgeFilesLines
* Merge RubyGems/Bundler masterHiroshi SHIBATA2022-12-121-1/+1
| | | | from https://github.com/rubygems/rubygems/commit/bfb0ae69776069155d2092702bfbb5a12617d85a
* [rubygems/rubygems] This sorting seems unnecessary tooDavid Rodríguez2022-09-121-1/+0
| | | | https://github.com/rubygems/rubygems/commit/823cb1fef9
* [rubygems/rubygems] Bundler: change error/warning message for multiple ↵Takuya Noguchi2022-07-191-2/+2
| | | | | | | | global sources Signed-off-by: Takuya Noguchi <takninnovationresearch@gmail.com> https://github.com/rubygems/rubygems/commit/316564b8fc
* Merge RubyGems and Bundler masterHiroshi SHIBATA2022-07-131-1/+1
|
* Sync RubyGems & Bundler with upstream repoDavid Rodríguez2022-06-241-3/+1
|
* [rubygems/rubygems] Skip duplicated dependency warning for gemspec dev depsDavid Rodríguez2022-06-011-7/+5
| | | | | | | | | | | Generally this warning is skipped for gemspec development dependencies. I think because it's common to override them in the Gemfile to change the source, for example. But the order of conditions was not correct and the warning was still being printed in one case. https://github.com/rubygems/rubygems/commit/da9d1d6a3f
* Merge RubyGems and Bundler HEADHiroshi SHIBATA2022-05-201-1/+1
| | | | https://github.com/rubygems/rubygems/commit/125415593ead9ab69a9f0bb5392c9d7ec61b1f51
* Track RubyGems 3.4.0dev and Bundler 2.4.0devHiroshi SHIBATA2021-12-271-1/+1
|
* Check if `Kernel#untaint` is defined instead of version comparisonNobuyoshi Nakada2021-12-271-1/+1
| | | | Probably `RUBY_VERSION` seems overwritten somewhere in the tests.
* [rubygems/rubygems] Cancel deprecation of custom git sourcesDavid Rodríguez2021-12-081-27/+0
| | | | https://github.com/rubygems/rubygems/commit/99cd6e0627
* [rubygems/rubygems] Feature: accept pull request URLs as github sourceJean Boussier2021-12-061-3/+18
| | | | | | | | | | | | | | | | | | | | | | | Very often github source is used to temporarily use a modified gem while a PR upstream is being reviewed. So for instance https://github.com/ruby/bigdecimal/pull/211 will look like: ```ruby gem "bigdecimal", github: "casperisfine/bigdecimal", branch: "git-gem" # https://github.com/ruby/bigdecimal/pull/200 ``` It's annoying because you have to fiddle with the branch name, which is copied as `casperisfine:git-gem`, etc etc. If I could simply use the PR URL like this: ``` gem "bigdecimal", github: "https://github.com/ruby/bigdecimal/pull/211" ``` It would make a very common task for me so much simpler. https://github.com/rubygems/rubygems/commit/517c527751
* [rubygems/rubygems] typos in UI messages: fix a couple missing spaces ↵Tim Sutton2021-08-311-1/+1
| | | | | | between sentence breaks https://github.com/rubygems/rubygems/commit/5cdda53382
* [rubygems/rubygems] Refactor Bundler::Dsl#check_rubygems_source_safety to ↵Daniel Niknam2021-07-271-5/+11
| | | | | | | | | | | | | | | | | improve readability `check_rubygems_source_safety` is responsible for: 1. if there are multiple global sources - for bundle 3.x raise an error - for bundle 2.x print a warning 2. print a warning if there is no explicit global source The second responsibility was added recently and now the logic could be extracted to improve readability. Conditions are still live in the `check_rubygems_source_safety` method since we don't want to call both functions always and that would help us achieve that. https://github.com/rubygems/rubygems/commit/f3d7e946ee
* [rubygems/rubygems] Deprecate Gemfile without an explicit global sourceDaniel Niknam2021-07-271-0/+7
| | | | | | Raise a warning when parsing a Gemfile and it doesn't have a global source. Gemfiles like this, specially now that rubygems sources are are no longer merged into a single source for security, are very confusing because they generate a different lockfile depending on the gems you have locally installed. This is because bundler always use an implicit global source that defaults to locally installed gems. https://github.com/rubygems/rubygems/commit/b7523ad21c
* [rubygems/rubygems] Fix development gem unintentionally removed on an edge caseDavid Rodríguez2021-07-161-25/+26
| | | | | | | | | | | When a development dependency was duplicated inside the gemspec and Gemfile with the same requirements, we went from printing a warning to removing the gem altogether. This change makes it not print a warning, but don't remove the gem either. https://github.com/rubygems/rubygems/commit/8bb2488131
* Merge RubyGems/Bundler master from 8459ebd6ad65ce3397233416dc64083ae7572bb9Hiroshi SHIBATA2021-07-141-20/+16
|
* Sync RubyGems and Bundler with upstreamHiroshi SHIBATA2021-07-071-11/+3
|
* Merge the master branch of BundlerHiroshi SHIBATA2021-04-151-6/+3
|
* Sync latest development version of bundler & rubygemsDavid Rodríguez2021-03-081-22/+36
|
* Merge bundler-2.2.0.rc.2Hiroshi SHIBATA2020-10-151-4/+4
|
* Sync Bundler PR #3624Hiroshi SHIBATA2020-05-221-3/+0
|
* Update the bundler version with master branchHiroshi SHIBATA2020-05-131-2/+1
|
* Merge Bundler 2.1.0.pre.3Hiroshi SHIBATA2019-11-111-1/+1
| | | | | | | | | | | | | | | 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] Bundler displays a duplicate gem entries warning even if ↵David Stosik2019-08-181-1/+1
| | | | | | gems only appear once per group https://github.com/bundler/bundler/commit/d18a83109e
* Merge bundler master from upstream.Hiroshi SHIBATA2019-06-091-8/+3
| | | | Pick from 8dd59e3ba97eb80a599f8149f31bf40773b69dc0
* Merge Bundler 2.1.0.pre.1 as developed version from upstream.hsbt2019-04-141-35/+16
| | | | | | 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-041-8/+8
| | | | git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66710 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
* Merge Bundler 1.17.2 from upstream.hsbt2018-12-111-1/+1
| | | | git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66338 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
* Downgrade Bundler 1.17.x from 2.0.0.hsbt2018-12-111-7/+7
| | | | | | | | 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 bundler-2.0.0.pre.2 from upstream.hsbt2018-11-271-2/+2
| | | | git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66036 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
* Merge Bundler-2.0.0.pre1 from upstream.hsbt2018-11-121-5/+5
| | | | git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@65672 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
* Added bundler as default gems. Revisit [Feature #12733]hsbt2018-11-021-0/+615
| | | | | | | | | | | * 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-221-599/+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
* Update bundled bundler to 1.16.0.hsbt2017-11-011-62/+97
| | | | | | | * 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-081-0/+564
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
View Lorry Controller Status