bundler 1.16.1 → 1.17.3

Sign up to get free protection for your applications and to get access to all the features.

Potentially problematic release.


This version of bundler might be problematic. Click here for more details.

Files changed (143) hide show
  1. checksums.yaml +5 -5
  2. data/CHANGELOG.md +195 -0
  3. data/README.md +5 -1
  4. data/bundler.gemspec +9 -2
  5. data/lib/bundler/build_metadata.rb +19 -4
  6. data/lib/bundler/cli/add.rb +15 -5
  7. data/lib/bundler/cli/binstubs.rb +8 -2
  8. data/lib/bundler/cli/check.rb +1 -1
  9. data/lib/bundler/cli/doctor.rb +47 -1
  10. data/lib/bundler/cli/exec.rb +4 -4
  11. data/lib/bundler/cli/gem.rb +5 -2
  12. data/lib/bundler/cli/init.rb +5 -0
  13. data/lib/bundler/cli/install.rb +10 -7
  14. data/lib/bundler/cli/list.rb +41 -5
  15. data/lib/bundler/cli/outdated.rb +8 -2
  16. data/lib/bundler/cli/pristine.rb +4 -0
  17. data/lib/bundler/cli/remove.rb +18 -0
  18. data/lib/bundler/cli/update.rb +3 -3
  19. data/lib/bundler/cli.rb +66 -22
  20. data/lib/bundler/compact_index_client/updater.rb +10 -1
  21. data/lib/bundler/current_ruby.rb +8 -1
  22. data/lib/bundler/definition.rb +48 -39
  23. data/lib/bundler/dep_proxy.rb +2 -2
  24. data/lib/bundler/dependency.rb +3 -2
  25. data/lib/bundler/deprecate.rb +2 -1
  26. data/lib/bundler/dsl.rb +19 -3
  27. data/lib/bundler/endpoint_specification.rb +1 -1
  28. data/lib/bundler/env.rb +10 -8
  29. data/lib/bundler/feature_flag.rb +7 -0
  30. data/lib/bundler/fetcher/downloader.rb +10 -5
  31. data/lib/bundler/fetcher/index.rb +2 -2
  32. data/lib/bundler/fetcher.rb +3 -3
  33. data/lib/bundler/friendly_errors.rb +2 -0
  34. data/lib/bundler/gem_helper.rb +1 -1
  35. data/lib/bundler/gem_version_promoter.rb +16 -2
  36. data/lib/bundler/injector.rb +173 -14
  37. data/lib/bundler/installer/gem_installer.rb +9 -2
  38. data/lib/bundler/installer/parallel_installer.rb +6 -1
  39. data/lib/bundler/installer.rb +41 -10
  40. data/lib/bundler/lazy_specification.rb +1 -1
  41. data/lib/bundler/mirror.rb +2 -2
  42. data/lib/bundler/plugin/events.rb +61 -0
  43. data/lib/bundler/plugin/index.rb +7 -2
  44. data/lib/bundler/plugin.rb +12 -5
  45. data/lib/bundler/process_lock.rb +1 -1
  46. data/lib/bundler/resolver/spec_group.rb +0 -5
  47. data/lib/bundler/resolver.rb +11 -10
  48. data/lib/bundler/ruby_version.rb +1 -1
  49. data/lib/bundler/rubygems_gem_installer.rb +7 -0
  50. data/lib/bundler/rubygems_integration.rb +9 -3
  51. data/lib/bundler/runtime.rb +10 -4
  52. data/lib/bundler/settings/validator.rb +23 -0
  53. data/lib/bundler/settings.rb +24 -3
  54. data/lib/bundler/shared_helpers.rb +33 -5
  55. data/lib/bundler/source/git/git_proxy.rb +6 -1
  56. data/lib/bundler/source/git.rb +2 -1
  57. data/lib/bundler/source/metadata.rb +2 -3
  58. data/lib/bundler/source/rubygems/remote.rb +4 -1
  59. data/lib/bundler/source/rubygems.rb +11 -2
  60. data/lib/bundler/source.rb +9 -9
  61. data/lib/bundler/spec_set.rb +4 -1
  62. data/lib/bundler/templates/Executable +1 -1
  63. data/lib/bundler/templates/newgem/lib/newgem.rb.tt +1 -0
  64. data/lib/bundler/templates/newgem/newgem.gemspec.tt +8 -2
  65. data/lib/bundler/templates/newgem/travis.yml.tt +2 -0
  66. data/lib/bundler/ui/shell.rb +3 -1
  67. data/lib/bundler/vendor/molinillo/lib/molinillo/dependency_graph/vertex.rb +11 -1
  68. data/lib/bundler/vendor/molinillo/lib/molinillo/errors.rb +7 -2
  69. data/lib/bundler/vendor/molinillo/lib/molinillo/gem_metadata.rb +1 -1
  70. data/lib/bundler/version.rb +1 -1
  71. data/lib/bundler.rb +38 -16
  72. data/man/bundle-add.1 +18 -3
  73. data/man/bundle-add.1.txt +17 -5
  74. data/man/bundle-add.ronn +13 -2
  75. data/man/bundle-binstubs.1 +4 -4
  76. data/man/bundle-binstubs.1.txt +4 -4
  77. data/man/bundle-binstubs.ronn +3 -3
  78. data/man/bundle-check.1 +4 -4
  79. data/man/bundle-check.1.txt +6 -5
  80. data/man/bundle-check.ronn +3 -3
  81. data/man/bundle-clean.1 +1 -1
  82. data/man/bundle-clean.1.txt +1 -1
  83. data/man/bundle-config.1 +48 -6
  84. data/man/bundle-config.1.txt +64 -26
  85. data/man/bundle-config.ronn +34 -9
  86. data/man/bundle-doctor.1 +44 -0
  87. data/man/bundle-doctor.1.txt +44 -0
  88. data/man/bundle-doctor.ronn +33 -0
  89. data/man/bundle-exec.1 +4 -4
  90. data/man/bundle-exec.1.txt +9 -9
  91. data/man/bundle-exec.ronn +3 -3
  92. data/man/bundle-gem.1 +2 -2
  93. data/man/bundle-gem.1.txt +2 -2
  94. data/man/bundle-gem.ronn +1 -1
  95. data/man/bundle-info.1 +1 -1
  96. data/man/bundle-info.1.txt +1 -1
  97. data/man/bundle-init.1 +9 -4
  98. data/man/bundle-init.1.txt +16 -6
  99. data/man/bundle-init.ronn +15 -4
  100. data/man/bundle-inject.1 +4 -4
  101. data/man/bundle-inject.1.txt +5 -5
  102. data/man/bundle-inject.ronn +3 -3
  103. data/man/bundle-install.1 +7 -4
  104. data/man/bundle-install.1.txt +119 -108
  105. data/man/bundle-install.ronn +13 -4
  106. data/man/bundle-list.1 +32 -2
  107. data/man/bundle-list.1.txt +24 -2
  108. data/man/bundle-list.ronn +19 -1
  109. data/man/bundle-lock.1 +2 -2
  110. data/man/bundle-lock.1.txt +2 -2
  111. data/man/bundle-lock.ronn +1 -1
  112. data/man/bundle-open.1 +1 -1
  113. data/man/bundle-open.1.txt +1 -1
  114. data/man/bundle-outdated.1 +7 -3
  115. data/man/bundle-outdated.1.txt +11 -7
  116. data/man/bundle-outdated.ronn +5 -1
  117. data/man/bundle-package.1 +3 -3
  118. data/man/bundle-package.1.txt +6 -6
  119. data/man/bundle-package.ronn +3 -3
  120. data/man/bundle-platform.1 +1 -1
  121. data/man/bundle-platform.1.txt +1 -1
  122. data/man/bundle-pristine.1 +1 -1
  123. data/man/bundle-pristine.1.txt +1 -1
  124. data/man/bundle-remove.1 +31 -0
  125. data/man/bundle-remove.1.txt +34 -0
  126. data/man/bundle-remove.ronn +23 -0
  127. data/man/bundle-show.1 +3 -3
  128. data/man/bundle-show.1.txt +6 -4
  129. data/man/bundle-show.ronn +3 -2
  130. data/man/bundle-update.1 +17 -13
  131. data/man/bundle-update.1.txt +68 -63
  132. data/man/bundle-update.ronn +19 -15
  133. data/man/bundle-viz.1 +2 -2
  134. data/man/bundle-viz.1.txt +3 -2
  135. data/man/bundle-viz.ronn +1 -1
  136. data/man/bundle.1 +32 -28
  137. data/man/bundle.1.txt +31 -28
  138. data/man/bundle.ronn +30 -27
  139. data/man/gemfile.5 +19 -9
  140. data/man/gemfile.5.ronn +24 -9
  141. data/man/gemfile.5.txt +114 -97
  142. data/man/index.txt +2 -0
  143. metadata +16 -3
data/man/gemfile.5.txt CHANGED
@@ -40,8 +40,8 @@ GLOBAL SOURCES
40
40
  option or a source block.
41
41
 
42
42
  CREDENTIALS
43
- Some gem sources require a username and password. Use [bundle con-
44
- fig(1)][bundle-config] to set the username and password for any of the
43
+ Some gem sources require a username and password. Use bundle config(1)
44
+ bundle-config.1.html to set the username and password for any of the
45
45
  sources that need it. The command must be run once on each computer
46
46
  that will install the Gemfile, but this keeps the credentials from
47
47
  being stored in plain text in version control.
@@ -71,8 +71,9 @@ RUBY
71
71
 
72
72
  VERSION (required)
73
73
  The version of Ruby that your application requires. If your application
74
- requires an alternate Ruby engine, such as JRuby or Rubinius, this
75
- should be the Ruby version that the engine is compatible with.
74
+ requires an alternate Ruby engine, such as JRuby, Rubinius or Truf-
75
+ fleRuby, this should be the Ruby version that the engine is compatible
76
+ with.
76
77
 
77
78
 
78
79
 
@@ -81,30 +82,30 @@ RUBY
81
82
 
82
83
 
83
84
  ENGINE
84
- Each application may specify a Ruby engine. If an engine is specified,
85
+ Each application may specify a Ruby engine. If an engine is specified,
85
86
  an engine version must also be specified.
86
87
 
87
- What exactly is an Engine? - A Ruby engine is an implementation of the
88
+ What exactly is an Engine? - A Ruby engine is an implementation of the
88
89
  Ruby language.
89
90
 
90
- o For background: the reference or original implementation of the
91
- Ruby programming language is called Matz's Ruby Interpreter
92
- https://en.wikipedia.org/wiki/Ruby_MRI, or MRI for short. This is
93
- named after Ruby creator Yukihiro Matsumoto, also known as Matz.
94
- MRI is also known as CRuby, because it is written in C. MRI is the
91
+ o For background: the reference or original implementation of the
92
+ Ruby programming language is called Matz's Ruby Interpreter
93
+ https://en.wikipedia.org/wiki/Ruby_MRI, or MRI for short. This is
94
+ named after Ruby creator Yukihiro Matsumoto, also known as Matz.
95
+ MRI is also known as CRuby, because it is written in C. MRI is the
95
96
  most widely used Ruby engine.
96
97
 
97
- o Other implementations https://www.ruby-lang.org/en/about/ of Ruby
98
+ o Other implementations https://www.ruby-lang.org/en/about/ of Ruby
98
99
  exist. Some of the more well-known implementations include Rubinius
99
- https://rubinius.com/, and JRuby http://jruby.org/. Rubinius is an
100
- alternative implementation of Ruby written in Ruby. JRuby is an
101
- implementation of Ruby on the JVM, short for Java Virtual Machine.
100
+ https://rubinius.com/, and JRuby http://jruby.org/. Rubinius is an
101
+ alternative implementation of Ruby written in Ruby. JRuby is an
102
+ implementation of Ruby on the JVM, short for Java Virtual Machine.
102
103
 
103
104
 
104
105
 
105
106
  ENGINE VERSION
106
- Each application may specify a Ruby engine version. If an engine ver-
107
- sion is specified, an engine must also be specified. If the engine is
107
+ Each application may specify a Ruby engine version. If an engine ver-
108
+ sion is specified, an engine must also be specified. If the engine is
108
109
  "ruby" the engine version specified must match the Ruby version.
109
110
 
110
111
 
@@ -146,9 +147,9 @@ GEMS
146
147
 
147
148
 
148
149
  REQUIRE AS
149
- Each gem MAY specify files that should be used when autorequiring via
150
- Bundler.require. You may pass an array with multiple files or true if
151
- file you want required has same name as gem or false to prevent any
150
+ Each gem MAY specify files that should be used when autorequiring via
151
+ Bundler.require. You may pass an array with multiple files or true if
152
+ file you want required has same name as gem or false to prevent any
152
153
  file from being autorequired.
153
154
 
154
155
 
@@ -159,7 +160,7 @@ GEMS
159
160
 
160
161
 
161
162
 
162
- The argument defaults to the name of the gem. For example, these are
163
+ The argument defaults to the name of the gem. For example, these are
163
164
  identical:
164
165
 
165
166
 
@@ -171,8 +172,8 @@ GEMS
171
172
 
172
173
 
173
174
  GROUPS
174
- Each gem MAY specify membership in one or more groups. Any gem that
175
- does not specify membership in any group is placed in the default
175
+ Each gem MAY specify membership in one or more groups. Any gem that
176
+ does not specify membership in any group is placed in the default
176
177
  group.
177
178
 
178
179
 
@@ -182,7 +183,7 @@ GEMS
182
183
 
183
184
 
184
185
 
185
- The Bundler runtime allows its two main methods, Bundler.setup and
186
+ The Bundler runtime allows its two main methods, Bundler.setup and
186
187
  Bundler.require, to limit their impact to particular groups.
187
188
 
188
189
 
@@ -202,9 +203,9 @@ GEMS
202
203
 
203
204
 
204
205
 
205
- The Bundler CLI allows you to specify a list of groups whose gems bun-
206
- dle install should not install with the --without option. To specify
207
- multiple groups to ignore, specify a list of groups separated by spa-
206
+ The Bundler CLI allows you to specify a list of groups whose gems bun-
207
+ dle install should not install with the --without option. To specify
208
+ multiple groups to ignore, specify a list of groups separated by spa-
208
209
  ces.
209
210
 
210
211
 
@@ -216,44 +217,47 @@ GEMS
216
217
 
217
218
  After running bundle install --without test, bundler will remember that
218
219
  you excluded the test group in the last installation. The next time you
219
- run bundle install, without any --without option, bundler will recall
220
+ run bundle install, without any --without option, bundler will recall
220
221
  it.
221
222
 
222
- Also, calling Bundler.setup with no parameters, or calling require
223
- "bundler/setup" will setup all groups except for the ones you excluded
223
+ Also, calling Bundler.setup with no parameters, or calling require
224
+ "bundler/setup" will setup all groups except for the ones you excluded
224
225
  via --without (since they are not available).
225
226
 
226
- Note that on bundle install, bundler downloads and evaluates all gems,
227
- in order to create a single canonical list of all of the required gems
228
- and their dependencies. This means that you cannot list different ver-
229
- sions of the same gems in different groups. For more details, see
227
+ Note that on bundle install, bundler downloads and evaluates all gems,
228
+ in order to create a single canonical list of all of the required gems
229
+ and their dependencies. This means that you cannot list different ver-
230
+ sions of the same gems in different groups. For more details, see
230
231
  Understanding Bundler http://bundler.io/rationale.html.
231
232
 
232
233
  PLATFORMS
233
- If a gem should only be used in a particular platform or set of plat-
234
- forms, you can specify them. Platforms are essentially identical to
235
- groups, except that you do not need to use the --without install-time
234
+ If a gem should only be used in a particular platform or set of plat-
235
+ forms, you can specify them. Platforms are essentially identical to
236
+ groups, except that you do not need to use the --without install-time
236
237
  flag to exclude groups of gems for other platforms.
237
238
 
238
239
  There are a number of Gemfile platforms:
239
240
 
240
- ruby C Ruby (MRI) or Rubinius, but NOT Windows
241
+ ruby C Ruby (MRI), Rubinius or TruffleRuby, but NOT Windows
241
242
 
242
- mri Same as ruby, but not Rubinius
243
+ mri Same as ruby, but only C Ruby (MRI)
243
244
 
244
245
  mingw Windows 32 bit 'mingw32' platform (aka RubyInstaller)
245
246
 
246
247
  x64_mingw
247
248
  Windows 64 bit 'mingw32' platform (aka RubyInstaller x64)
248
249
 
249
- rbx Same as ruby, but only Rubinius (not MRI)
250
+ rbx Rubinius
250
251
 
251
252
  jruby JRuby
252
253
 
254
+ truffleruby
255
+ TruffleRuby
256
+
253
257
  mswin Windows
254
258
 
255
- You can restrict further by platform and version for all platforms
256
- except for rbx, jruby, and mswin.
259
+ You can restrict further by platform and version for all platforms
260
+ except for rbx, jruby, truffleruby and mswin.
257
261
 
258
262
  To specify a version in addition to a platform, append the version num-
259
263
  ber without the delimiter to the platform. For example, to specify that
@@ -286,12 +290,12 @@ GEMS
286
290
 
287
291
 
288
292
 
289
- All operations involving groups (bundle install, Bundler.setup,
290
- Bundler.require) behave exactly the same as if any groups not matching
291
- the current platform were explicitly excluded.
293
+ All operations involving groups (bundle install bundle-install.1.html,
294
+ Bundler.setup, Bundler.require) behave exactly the same as if any
295
+ groups not matching the current platform were explicitly excluded.
292
296
 
293
297
  SOURCE
294
- You can select an alternate Rubygems repository for a gem using the
298
+ You can select an alternate Rubygems repository for a gem using the
295
299
  ':source' option.
296
300
 
297
301
 
@@ -300,18 +304,24 @@ GEMS
300
304
 
301
305
 
302
306
 
303
- This forces the gem to be loaded from this source and ignores any
304
- global sources declared at the top level of the file. If the gem does
307
+ This forces the gem to be loaded from this source and ignores any
308
+ global sources declared at the top level of the file. If the gem does
305
309
  not exist in this source, it will not be installed.
306
310
 
307
311
  Bundler will search for child dependencies of this gem by first looking
308
312
  in the source selected for the parent, but if they are not found there,
309
- it will fall back on global sources using the ordering described in
313
+ it will fall back on global sources using the ordering described in
310
314
  SOURCE PRIORITY.
311
315
 
312
- Selecting a specific source repository this way also suppresses the
316
+ Selecting a specific source repository this way also suppresses the
313
317
  ambiguous gem warning described above in GLOBAL SOURCES (#source).
314
318
 
319
+ Using the :source option for an individual gem will also make that
320
+ source available as a possible global source for any other gems which
321
+ do not specify explicit sources. Thus, when adding gems with explicit
322
+ sources, it is recommended that you also ensure all other gems in the
323
+ Gemfile are using explicit sources.
324
+
315
325
  GIT
316
326
  If necessary, you can specify that a gem is located at a particular git
317
327
  repository using the :git parameter. The repository can be accessed via
@@ -327,27 +337,27 @@ GEMS
327
337
  If using SSH, the user that you use to run bundle install MUST have the
328
338
  appropriate keys available in their $HOME/.ssh.
329
339
 
330
- NOTE: http:// and git:// URLs should be avoided if at all possible.
331
- These protocols are unauthenticated, so a man-in-the-middle attacker
332
- can deliver malicious code and compromise your system. HTTPS and SSH
340
+ NOTE: http:// and git:// URLs should be avoided if at all possible.
341
+ These protocols are unauthenticated, so a man-in-the-middle attacker
342
+ can deliver malicious code and compromise your system. HTTPS and SSH
333
343
  are strongly preferred.
334
344
 
335
- The group, platforms, and require options are available and behave
345
+ The group, platforms, and require options are available and behave
336
346
  exactly the same as they would for a normal gem.
337
347
 
338
- A git repository SHOULD have at least one file, at the root of the
339
- directory containing the gem, with the extension .gemspec. This file
340
- MUST contain a valid gem specification, as expected by the gem build
348
+ A git repository SHOULD have at least one file, at the root of the
349
+ directory containing the gem, with the extension .gemspec. This file
350
+ MUST contain a valid gem specification, as expected by the gem build
341
351
  command.
342
352
 
343
- If a git repository does not have a .gemspec, bundler will attempt to
353
+ If a git repository does not have a .gemspec, bundler will attempt to
344
354
  create one, but it will not contain any dependencies, executables, or C
345
- extension compilation instructions. As a result, it may fail to prop-
355
+ extension compilation instructions. As a result, it may fail to prop-
346
356
  erly integrate into your application.
347
357
 
348
- If a git repository does have a .gemspec for the gem you attached it
349
- to, a version specifier, if provided, means that the git repository is
350
- only valid if the .gemspec specifies a version matching the version
358
+ If a git repository does have a .gemspec for the gem you attached it
359
+ to, a version specifier, if provided, means that the git repository is
360
+ only valid if the .gemspec specifies a version matching the version
351
361
  specifier. If not, bundler will print a warning.
352
362
 
353
363
 
@@ -358,19 +368,19 @@ GEMS
358
368
 
359
369
 
360
370
 
361
- If a git repository does not have a .gemspec for the gem you attached
371
+ If a git repository does not have a .gemspec for the gem you attached
362
372
  it to, a version specifier MUST be provided. Bundler will use this ver-
363
373
  sion in the simple .gemspec it creates.
364
374
 
365
375
  Git repositories support a number of additional options.
366
376
 
367
377
  branch, tag, and ref
368
- You MUST only specify at most one of these options. The default
378
+ You MUST only specify at most one of these options. The default
369
379
  is :branch => "master"
370
380
 
371
381
  For example:
372
382
 
373
- git "https://github.com/rails/rails.git", :branch => "5-0-sta-
383
+ git "https://github.com/rails/rails.git", :branch => "5-0-sta-
374
384
  ble" do
375
385
 
376
386
  git "https://github.com/rails/rails.git", :tag => "v5.0.0" do
@@ -378,14 +388,14 @@ GEMS
378
388
  git "https://github.com/rails/rails.git", :ref => "4aded" do
379
389
 
380
390
  submodules
381
- For reference, a git submodule
391
+ For reference, a git submodule
382
392
  https://git-scm.com/book/en/v2/Git-Tools-Submodules lets you
383
- have another git repository within a subfolder of your reposi-
393
+ have another git repository within a subfolder of your reposi-
384
394
  tory. Specify :submodules => true to cause bundler to expand any
385
395
  submodules included in the git repository
386
396
 
387
- If a git repository contains multiple .gemspecs, each .gemspec repre-
388
- sents a gem located at the same place in the file system as the .gem-
397
+ If a git repository contains multiple .gemspecs, each .gemspec repre-
398
+ sents a gem located at the same place in the file system as the .gem-
389
399
  spec.
390
400
 
391
401
 
@@ -400,16 +410,16 @@ GEMS
400
410
 
401
411
 
402
412
 
403
- To install a gem located in a git repository, bundler changes to the
404
- directory containing the gemspec, runs gem build name.gemspec and then
413
+ To install a gem located in a git repository, bundler changes to the
414
+ directory containing the gemspec, runs gem build name.gemspec and then
405
415
  installs the resulting gem. The gem build command, which comes standard
406
- with Rubygems, evaluates the .gemspec in the context of the directory
416
+ with Rubygems, evaluates the .gemspec in the context of the directory
407
417
  in which it is located.
408
418
 
409
419
  GIT SOURCE
410
- A custom git source can be defined via the git_source method. Provide
411
- the source's name as an argument, and a block which receives a single
412
- argument and interpolates it into a string to return the full repo
420
+ A custom git source can be defined via the git_source method. Provide
421
+ the source's name as an argument, and a block which receives a single
422
+ argument and interpolates it into a string to return the full repo
413
423
  address:
414
424
 
415
425
 
@@ -432,10 +442,10 @@ GEMS
432
442
  rently expands to an insecure git:// URL. This allows a man-in-the-mid-
433
443
  dle attacker to compromise your system.
434
444
 
435
- If the git repository you want to use is hosted on GitHub and is pub-
436
- lic, you can use the :github shorthand to specify the github username
437
- and repository name (without the trailing ".git"), separated by a
438
- slash. If both the username and repository name are the same, you can
445
+ If the git repository you want to use is hosted on GitHub and is pub-
446
+ lic, you can use the :github shorthand to specify the github username
447
+ and repository name (without the trailing ".git"), separated by a
448
+ slash. If both the username and repository name are the same, you can
439
449
  omit one.
440
450
 
441
451
 
@@ -458,7 +468,7 @@ GEMS
458
468
 
459
469
  GIST
460
470
  If the git repository you want to use is hosted as a Github Gist and is
461
- public, you can use the :gist shorthand to specify the gist identifier
471
+ public, you can use the :gist shorthand to specify the gist identifier
462
472
  (without the trailing ".git").
463
473
 
464
474
 
@@ -475,14 +485,14 @@ GEMS
475
485
 
476
486
 
477
487
 
478
- Since the gist method is a specialization of git_source, it accepts a
488
+ Since the gist method is a specialization of git_source, it accepts a
479
489
  :branch named argument.
480
490
 
481
491
  BITBUCKET
482
- If the git repository you want to use is hosted on Bitbucket and is
483
- public, you can use the :bitbucket shorthand to specify the bitbucket
484
- username and repository name (without the trailing ".git"), separated
485
- by a slash. If both the username and repository name are the same, you
492
+ If the git repository you want to use is hosted on Bitbucket and is
493
+ public, you can use the :bitbucket shorthand to specify the bitbucket
494
+ username and repository name (without the trailing ".git"), separated
495
+ by a slash. If both the username and repository name are the same, you
486
496
  can omit one.
487
497
 
488
498
 
@@ -500,19 +510,19 @@ GEMS
500
510
 
501
511
 
502
512
 
503
- Since the bitbucket method is a specialization of git_source, it
513
+ Since the bitbucket method is a specialization of git_source, it
504
514
  accepts a :branch named argument.
505
515
 
506
516
  PATH
507
- You can specify that a gem is located in a particular location on the
517
+ You can specify that a gem is located in a particular location on the
508
518
  file system. Relative paths are resolved relative to the directory con-
509
519
  taining the Gemfile.
510
520
 
511
- Similar to the semantics of the :git option, the :path option requires
512
- that the directory in question either contains a .gemspec for the gem,
521
+ Similar to the semantics of the :git option, the :path option requires
522
+ that the directory in question either contains a .gemspec for the gem,
513
523
  or that you specify an explicit version that bundler should use.
514
524
 
515
- Unlike :git, bundler does not compile C extensions for gems specified
525
+ Unlike :git, bundler does not compile C extensions for gems specified
516
526
  as paths.
517
527
 
518
528
 
@@ -522,8 +532,8 @@ GEMS
522
532
 
523
533
 
524
534
  If you would like to use multiple local gems directly from the filesys-
525
- tem, you can set a global path option to the path containing the gem's
526
- files. This will automatically load gemspec files from subdirectories.
535
+ tem, you can set a global path option to the path containing the gem's
536
+ files. This will automatically load gemspec files from subdirectories.
527
537
 
528
538
 
529
539
 
@@ -562,14 +572,21 @@ BLOCK FORM OF SOURCE, GIT, PATH, GROUP and PLATFORMS
562
572
 
563
573
 
564
574
 
565
- In the case of the group block form the :optional option can be given
566
- to prevent a group from being installed unless listed in the --with
575
+ In the case of the group block form the :optional option can be given
576
+ to prevent a group from being installed unless listed in the --with
567
577
  option given to the bundle install command.
568
578
 
569
- In the case of the git block form, the :ref, :branch, :tag, and :sub-
570
- modules options may be passed to the git method, and all gems in the
579
+ In the case of the git block form, the :ref, :branch, :tag, and :sub-
580
+ modules options may be passed to the git method, and all gems in the
571
581
  block will inherit those options.
572
582
 
583
+ The presence of a source block in a Gemfile also makes that source
584
+ available as a possible global source for any other gems which do not
585
+ specify explicit sources. Thus, when defining source blocks, it is rec-
586
+ ommended that you also ensure all other gems in the Gemfile are using
587
+ explicit sources, either via source blocks or :source directives on
588
+ individual gems.
589
+
573
590
  INSTALL_IF
574
591
  The install_if method allows gems to be installed based on a proc or
575
592
  lambda. This is especially useful for optional gems that can only be
@@ -633,4 +650,4 @@ SOURCE PRIORITY
633
650
 
634
651
 
635
652
 
636
- July 2017 GEMFILE(5)
653
+ November 2018 GEMFILE(5)
data/man/index.txt CHANGED
@@ -5,6 +5,7 @@ bundle-binstubs(1) bundle-binstubs.1
5
5
  bundle-check(1) bundle-check.1
6
6
  bundle-clean(1) bundle-clean.1
7
7
  bundle-config(1) bundle-config.1
8
+ bundle-doctor(1) bundle-doctor.1
8
9
  bundle-exec(1) bundle-exec.1
9
10
  bundle-gem(1) bundle-gem.1
10
11
  bundle-info(1) bundle-info.1
@@ -18,6 +19,7 @@ bundle-outdated(1) bundle-outdated.1
18
19
  bundle-package(1) bundle-package.1
19
20
  bundle-platform(1) bundle-platform.1
20
21
  bundle-pristine(1) bundle-pristine.1
22
+ bundle-remove(1) bundle-remove.1
21
23
  bundle-show(1) bundle-show.1
22
24
  bundle-update(1) bundle-update.1
23
25
  bundle-viz(1) bundle-viz.1
metadata CHANGED
@@ -1,11 +1,16 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: bundler
3
3
  version: !ruby/object:Gem::Version
4
- version: 1.16.1
4
+ version: 1.17.3
5
5
  platform: ruby
6
6
  authors:
7
7
  - André Arko
8
8
  - Samuel Giddins
9
+ - Colby Swandale
10
+ - Hiroshi Shibata
11
+ - David Rodríguez
12
+ - Grey Baker
13
+ - Stephanie Morillo
9
14
  - Chris Morris
10
15
  - James Wen
11
16
  - Tim Moore
@@ -17,7 +22,7 @@ authors:
17
22
  autorequire:
18
23
  bindir: exe
19
24
  cert_chain: []
20
- date: 2017-12-21 00:00:00.000000000 Z
25
+ date: 2018-12-27 00:00:00.000000000 Z
21
26
  dependencies:
22
27
  - !ruby/object:Gem::Dependency
23
28
  name: automatiek
@@ -148,6 +153,7 @@ files:
148
153
  - lib/bundler/cli/platform.rb
149
154
  - lib/bundler/cli/plugin.rb
150
155
  - lib/bundler/cli/pristine.rb
156
+ - lib/bundler/cli/remove.rb
151
157
  - lib/bundler/cli/show.rb
152
158
  - lib/bundler/cli/update.rb
153
159
  - lib/bundler/cli/viz.rb
@@ -198,6 +204,7 @@ files:
198
204
  - lib/bundler/plugin/api.rb
199
205
  - lib/bundler/plugin/api/source.rb
200
206
  - lib/bundler/plugin/dsl.rb
207
+ - lib/bundler/plugin/events.rb
201
208
  - lib/bundler/plugin/index.rb
202
209
  - lib/bundler/plugin/installer.rb
203
210
  - lib/bundler/plugin/installer/git.rb
@@ -350,6 +357,9 @@ files:
350
357
  - man/bundle-config.1
351
358
  - man/bundle-config.1.txt
352
359
  - man/bundle-config.ronn
360
+ - man/bundle-doctor.1
361
+ - man/bundle-doctor.1.txt
362
+ - man/bundle-doctor.ronn
353
363
  - man/bundle-exec.1
354
364
  - man/bundle-exec.1.txt
355
365
  - man/bundle-exec.ronn
@@ -389,6 +399,9 @@ files:
389
399
  - man/bundle-pristine.1
390
400
  - man/bundle-pristine.1.txt
391
401
  - man/bundle-pristine.ronn
402
+ - man/bundle-remove.1
403
+ - man/bundle-remove.1.txt
404
+ - man/bundle-remove.ronn
392
405
  - man/bundle-show.1
393
406
  - man/bundle-show.1.txt
394
407
  - man/bundle-show.ronn
@@ -429,7 +442,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
429
442
  version: 1.3.6
430
443
  requirements: []
431
444
  rubyforge_project:
432
- rubygems_version: 2.6.13
445
+ rubygems_version: 2.7.6
433
446
  signing_key:
434
447
  specification_version: 4
435
448
  summary: The best way to manage your application's dependencies