bundler 1.15.2 → 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 (286) hide show
  1. checksums.yaml +5 -5
  2. data/CHANGELOG.md +302 -0
  3. data/README.md +17 -8
  4. data/bundler.gemspec +25 -9
  5. data/exe/bundle +1 -1
  6. data/exe/bundle_ruby +4 -3
  7. data/lib/bundler/build_metadata.rb +53 -0
  8. data/lib/bundler/capistrano.rb +5 -0
  9. data/lib/bundler/cli/add.rb +15 -6
  10. data/lib/bundler/cli/binstubs.rb +17 -9
  11. data/lib/bundler/cli/cache.rb +5 -4
  12. data/lib/bundler/cli/check.rb +3 -5
  13. data/lib/bundler/cli/clean.rb +5 -6
  14. data/lib/bundler/cli/common.rb +11 -2
  15. data/lib/bundler/cli/config.rb +2 -1
  16. data/lib/bundler/cli/console.rb +2 -1
  17. data/lib/bundler/cli/doctor.rb +48 -1
  18. data/lib/bundler/cli/exec.rb +6 -5
  19. data/lib/bundler/cli/gem.rb +13 -8
  20. data/lib/bundler/cli/info.rb +0 -1
  21. data/lib/bundler/cli/init.rb +18 -6
  22. data/lib/bundler/cli/inject.rb +1 -0
  23. data/lib/bundler/cli/install.rb +64 -61
  24. data/lib/bundler/cli/issue.rb +1 -1
  25. data/lib/bundler/cli/list.rb +58 -0
  26. data/lib/bundler/cli/lock.rb +0 -1
  27. data/lib/bundler/cli/open.rb +2 -2
  28. data/lib/bundler/cli/outdated.rb +20 -9
  29. data/lib/bundler/cli/package.rb +9 -6
  30. data/lib/bundler/cli/platform.rb +1 -0
  31. data/lib/bundler/cli/plugin.rb +1 -0
  32. data/lib/bundler/cli/pristine.rb +20 -6
  33. data/lib/bundler/cli/remove.rb +18 -0
  34. data/lib/bundler/cli/show.rb +0 -1
  35. data/lib/bundler/cli/update.rb +35 -7
  36. data/lib/bundler/cli/viz.rb +1 -0
  37. data/lib/bundler/cli.rb +227 -89
  38. data/lib/bundler/compact_index_client/cache.rb +1 -2
  39. data/lib/bundler/compact_index_client/updater.rb +14 -4
  40. data/lib/bundler/compact_index_client.rb +1 -0
  41. data/lib/bundler/compatibility_guard.rb +14 -0
  42. data/lib/bundler/constants.rb +1 -0
  43. data/lib/bundler/current_ruby.rb +13 -5
  44. data/lib/bundler/definition.rb +192 -139
  45. data/lib/bundler/dep_proxy.rb +3 -1
  46. data/lib/bundler/dependency.rb +9 -9
  47. data/lib/bundler/deployment.rb +1 -1
  48. data/lib/bundler/deprecate.rb +15 -3
  49. data/lib/bundler/dsl.rb +115 -64
  50. data/lib/bundler/endpoint_specification.rb +10 -1
  51. data/lib/bundler/env.rb +90 -29
  52. data/lib/bundler/environment_preserver.rb +27 -6
  53. data/lib/bundler/errors.rb +1 -0
  54. data/lib/bundler/feature_flag.rb +46 -4
  55. data/lib/bundler/fetcher/base.rb +1 -0
  56. data/lib/bundler/fetcher/compact_index.rb +2 -11
  57. data/lib/bundler/fetcher/dependency.rb +2 -1
  58. data/lib/bundler/fetcher/downloader.rb +11 -5
  59. data/lib/bundler/fetcher/index.rb +3 -2
  60. data/lib/bundler/fetcher.rb +18 -11
  61. data/lib/bundler/friendly_errors.rb +6 -1
  62. data/lib/bundler/gem_helper.rb +19 -10
  63. data/lib/bundler/gem_helpers.rb +1 -0
  64. data/lib/bundler/gem_remote_fetcher.rb +1 -0
  65. data/lib/bundler/gem_tasks.rb +1 -0
  66. data/lib/bundler/gem_version_promoter.rb +17 -2
  67. data/lib/bundler/gemdeps.rb +1 -0
  68. data/lib/bundler/graph.rb +1 -0
  69. data/lib/bundler/index.rb +8 -8
  70. data/lib/bundler/injector.rb +192 -30
  71. data/lib/bundler/inline.rb +5 -7
  72. data/lib/bundler/installer/gem_installer.rb +11 -2
  73. data/lib/bundler/installer/parallel_installer.rb +78 -42
  74. data/lib/bundler/installer/standalone.rb +1 -0
  75. data/lib/bundler/installer.rb +138 -53
  76. data/lib/bundler/lazy_specification.rb +3 -2
  77. data/lib/bundler/lockfile_generator.rb +95 -0
  78. data/lib/bundler/lockfile_parser.rb +10 -4
  79. data/lib/bundler/match_platform.rb +1 -0
  80. data/lib/bundler/mirror.rb +8 -5
  81. data/lib/bundler/plugin/api/source.rb +9 -2
  82. data/lib/bundler/plugin/events.rb +61 -0
  83. data/lib/bundler/plugin/index.rb +7 -2
  84. data/lib/bundler/plugin/installer.rb +7 -6
  85. data/lib/bundler/plugin/source_list.rb +7 -8
  86. data/lib/bundler/plugin.rb +13 -5
  87. data/lib/bundler/process_lock.rb +24 -0
  88. data/lib/bundler/psyched_yaml.rb +10 -0
  89. data/lib/bundler/remote_specification.rb +1 -0
  90. data/lib/bundler/resolver/spec_group.rb +106 -0
  91. data/lib/bundler/resolver.rb +158 -195
  92. data/lib/bundler/retry.rb +1 -0
  93. data/lib/bundler/ruby_dsl.rb +1 -0
  94. data/lib/bundler/ruby_version.rb +2 -1
  95. data/lib/bundler/rubygems_ext.rb +5 -4
  96. data/lib/bundler/rubygems_gem_installer.rb +31 -1
  97. data/lib/bundler/rubygems_integration.rb +71 -32
  98. data/lib/bundler/runtime.rb +11 -9
  99. data/lib/bundler/settings/validator.rb +102 -0
  100. data/lib/bundler/settings.rb +200 -77
  101. data/lib/bundler/setup.rb +1 -0
  102. data/lib/bundler/shared_helpers.rb +131 -26
  103. data/lib/bundler/similarity_detector.rb +1 -0
  104. data/lib/bundler/source/gemspec.rb +1 -0
  105. data/lib/bundler/source/git/git_proxy.rb +21 -11
  106. data/lib/bundler/source/git.rb +24 -19
  107. data/lib/bundler/source/metadata.rb +62 -0
  108. data/lib/bundler/source/path/installer.rb +2 -0
  109. data/lib/bundler/source/path.rb +8 -8
  110. data/lib/bundler/source/rubygems/remote.rb +8 -2
  111. data/lib/bundler/source/rubygems.rb +161 -84
  112. data/lib/bundler/source.rb +36 -0
  113. data/lib/bundler/source_list.rb +75 -15
  114. data/lib/bundler/spec_set.rb +10 -5
  115. data/lib/bundler/ssl_certs/certificate_manager.rb +2 -1
  116. data/lib/bundler/stub_specification.rb +1 -0
  117. data/lib/bundler/templates/.document +1 -0
  118. data/lib/bundler/templates/Executable +12 -0
  119. data/lib/bundler/templates/Executable.bundler +105 -0
  120. data/lib/bundler/templates/Gemfile +1 -0
  121. data/lib/bundler/templates/gems.rb +8 -0
  122. data/lib/bundler/templates/newgem/README.md.tt +1 -1
  123. data/lib/bundler/templates/newgem/gitignore.tt +0 -1
  124. data/lib/bundler/templates/newgem/lib/newgem.rb.tt +1 -0
  125. data/lib/bundler/templates/newgem/newgem.gemspec.tt +12 -3
  126. data/lib/bundler/templates/newgem/rspec.tt +1 -0
  127. data/lib/bundler/templates/newgem/spec/newgem_spec.rb.tt +0 -2
  128. data/lib/bundler/templates/newgem/{.travis.yml.tt → travis.yml.tt} +2 -0
  129. data/lib/bundler/ui/rg_proxy.rb +1 -0
  130. data/lib/bundler/ui/shell.rb +17 -4
  131. data/lib/bundler/ui/silent.rb +1 -0
  132. data/lib/bundler/ui.rb +1 -0
  133. data/lib/bundler/uri_credentials_filter.rb +1 -0
  134. data/lib/bundler/vendor/fileutils/lib/fileutils.rb +1638 -0
  135. data/lib/bundler/vendor/molinillo/lib/molinillo/compatibility.rb +26 -0
  136. data/lib/bundler/vendor/molinillo/lib/molinillo/delegates/resolution_state.rb +7 -0
  137. data/lib/bundler/vendor/molinillo/lib/molinillo/delegates/specification_provider.rb +1 -0
  138. data/lib/bundler/vendor/molinillo/lib/molinillo/dependency_graph/action.rb +1 -0
  139. data/lib/bundler/vendor/molinillo/lib/molinillo/dependency_graph/add_edge_no_circular.rb +1 -0
  140. data/lib/bundler/vendor/molinillo/lib/molinillo/dependency_graph/add_vertex.rb +1 -0
  141. data/lib/bundler/vendor/molinillo/lib/molinillo/dependency_graph/delete_edge.rb +1 -0
  142. data/lib/bundler/vendor/molinillo/lib/molinillo/dependency_graph/detach_vertex_named.rb +1 -0
  143. data/lib/bundler/vendor/molinillo/lib/molinillo/dependency_graph/log.rb +1 -0
  144. data/lib/bundler/vendor/molinillo/lib/molinillo/dependency_graph/set_payload.rb +1 -0
  145. data/lib/bundler/vendor/molinillo/lib/molinillo/dependency_graph/tag.rb +1 -0
  146. data/lib/bundler/vendor/molinillo/lib/molinillo/dependency_graph/vertex.rb +15 -4
  147. data/lib/bundler/vendor/molinillo/lib/molinillo/dependency_graph.rb +3 -2
  148. data/lib/bundler/vendor/molinillo/lib/molinillo/errors.rb +75 -7
  149. data/lib/bundler/vendor/molinillo/lib/molinillo/gem_metadata.rb +2 -1
  150. data/lib/bundler/vendor/molinillo/lib/molinillo/modules/specification_provider.rb +1 -0
  151. data/lib/bundler/vendor/molinillo/lib/molinillo/modules/ui.rb +3 -1
  152. data/lib/bundler/vendor/molinillo/lib/molinillo/resolution.rb +491 -148
  153. data/lib/bundler/vendor/molinillo/lib/molinillo/resolver.rb +1 -0
  154. data/lib/bundler/vendor/molinillo/lib/molinillo/state.rb +8 -4
  155. data/lib/bundler/vendor/molinillo/lib/molinillo.rb +2 -0
  156. data/lib/bundler/vendor/net-http-persistent/lib/net/http/persistent.rb +1 -1
  157. data/lib/bundler/vendor/thor/lib/thor/actions/create_file.rb +1 -0
  158. data/lib/bundler/vendor/thor/lib/thor/actions/create_link.rb +1 -0
  159. data/lib/bundler/vendor/thor/lib/thor/actions/empty_directory.rb +9 -1
  160. data/lib/bundler/vendor/thor/lib/thor/actions/file_manipulation.rb +45 -8
  161. data/lib/bundler/vendor/thor/lib/thor/actions/inject_into_file.rb +9 -3
  162. data/lib/bundler/vendor/thor/lib/thor/actions.rb +6 -3
  163. data/lib/bundler/vendor/thor/lib/thor/base.rb +27 -4
  164. data/lib/bundler/vendor/thor/lib/thor/command.rb +9 -7
  165. data/lib/bundler/vendor/thor/lib/thor/core_ext/hash_with_indifferent_access.rb +12 -0
  166. data/lib/bundler/vendor/thor/lib/thor/group.rb +1 -1
  167. data/lib/bundler/vendor/thor/lib/thor/line_editor/basic.rb +2 -0
  168. data/lib/bundler/vendor/thor/lib/thor/parser/option.rb +5 -5
  169. data/lib/bundler/vendor/thor/lib/thor/parser/options.rb +6 -5
  170. data/lib/bundler/vendor/thor/lib/thor/runner.rb +6 -4
  171. data/lib/bundler/vendor/thor/lib/thor/shell/basic.rb +10 -9
  172. data/lib/bundler/vendor/thor/lib/thor/version.rb +1 -1
  173. data/lib/bundler/vendor/thor/lib/thor.rb +25 -8
  174. data/lib/bundler/vendored_fileutils.rb +9 -0
  175. data/lib/bundler/vendored_molinillo.rb +1 -0
  176. data/lib/bundler/vendored_persistent.rb +35 -0
  177. data/lib/bundler/vendored_thor.rb +1 -0
  178. data/lib/bundler/version.rb +6 -2
  179. data/lib/bundler/version_ranges.rb +1 -0
  180. data/lib/bundler/vlad.rb +5 -0
  181. data/lib/bundler/worker.rb +1 -0
  182. data/lib/bundler/yaml_serializer.rb +3 -3
  183. data/lib/bundler.rb +86 -52
  184. data/man/bundle-add.1 +18 -3
  185. data/man/bundle-add.1.txt +26 -14
  186. data/man/bundle-add.ronn +13 -2
  187. data/man/bundle-binstubs.1 +11 -1
  188. data/man/bundle-binstubs.1.txt +33 -18
  189. data/man/bundle-binstubs.ronn +15 -1
  190. data/man/bundle-check.1 +4 -4
  191. data/man/bundle-check.1.txt +15 -14
  192. data/man/bundle-check.ronn +3 -3
  193. data/man/bundle-clean.1 +1 -1
  194. data/man/bundle-clean.1.txt +10 -10
  195. data/man/bundle-config.1 +129 -29
  196. data/man/bundle-config.1.txt +285 -174
  197. data/man/bundle-config.ronn +167 -88
  198. data/man/bundle-doctor.1 +44 -0
  199. data/man/bundle-doctor.1.txt +44 -0
  200. data/man/bundle-doctor.ronn +33 -0
  201. data/man/bundle-exec.1 +6 -3
  202. data/man/bundle-exec.1.txt +78 -71
  203. data/man/bundle-exec.ronn +10 -3
  204. data/man/bundle-gem.1 +3 -3
  205. data/man/bundle-gem.1.txt +40 -39
  206. data/man/bundle-gem.ronn +2 -1
  207. data/man/bundle-info.1 +1 -1
  208. data/man/bundle-info.1.txt +8 -8
  209. data/man/bundle-init.1 +9 -4
  210. data/man/bundle-init.1.txt +23 -13
  211. data/man/bundle-init.ronn +15 -4
  212. data/man/bundle-inject.1 +4 -4
  213. data/man/bundle-inject.1.txt +10 -10
  214. data/man/bundle-inject.ronn +3 -3
  215. data/man/bundle-install.1 +31 -28
  216. data/man/bundle-install.1.txt +205 -194
  217. data/man/bundle-install.ronn +44 -35
  218. data/man/bundle-list.1 +50 -0
  219. data/man/bundle-list.1.txt +43 -0
  220. data/man/bundle-list.ronn +33 -0
  221. data/man/bundle-lock.1 +1 -1
  222. data/man/bundle-lock.1.txt +47 -47
  223. data/man/bundle-lock.ronn +1 -1
  224. data/man/bundle-open.1 +1 -1
  225. data/man/bundle-open.1.txt +7 -7
  226. data/man/bundle-outdated.1 +7 -3
  227. data/man/bundle-outdated.1.txt +40 -36
  228. data/man/bundle-outdated.ronn +6 -2
  229. data/man/bundle-package.1 +6 -3
  230. data/man/bundle-package.1.txt +44 -39
  231. data/man/bundle-package.ronn +7 -2
  232. data/man/bundle-platform.1 +1 -1
  233. data/man/bundle-platform.1.txt +13 -13
  234. data/man/bundle-pristine.1 +21 -3
  235. data/man/bundle-pristine.1.txt +33 -10
  236. data/man/bundle-pristine.ronn +24 -3
  237. data/man/bundle-remove.1 +31 -0
  238. data/man/bundle-remove.1.txt +34 -0
  239. data/man/bundle-remove.ronn +23 -0
  240. data/man/bundle-show.1 +3 -3
  241. data/man/bundle-show.1.txt +14 -12
  242. data/man/bundle-show.ronn +3 -2
  243. data/man/bundle-update.1 +13 -9
  244. data/man/bundle-update.1.txt +133 -130
  245. data/man/bundle-update.ronn +21 -17
  246. data/man/bundle-viz.1 +7 -7
  247. data/man/bundle-viz.1.txt +17 -15
  248. data/man/bundle-viz.ronn +6 -6
  249. data/man/bundle.1 +31 -23
  250. data/man/bundle.1.txt +63 -57
  251. data/man/bundle.ronn +35 -29
  252. data/man/gemfile.5 +44 -8
  253. data/man/gemfile.5.ronn +54 -8
  254. data/man/gemfile.5.txt +218 -165
  255. data/man/index.txt +25 -15
  256. metadata +36 -36
  257. data/.codeclimate.yml +0 -25
  258. data/.gitignore +0 -18
  259. data/.rspec +0 -3
  260. data/.rubocop.yml +0 -131
  261. data/.rubocop_todo.yml +0 -418
  262. data/.travis.yml +0 -122
  263. data/CODE_OF_CONDUCT.md +0 -42
  264. data/CONTRIBUTING.md +0 -17
  265. data/Rakefile +0 -338
  266. data/bin/rake +0 -19
  267. data/bin/rspec +0 -15
  268. data/bin/rubocop +0 -17
  269. data/bin/with_rubygems +0 -39
  270. data/doc/README.md +0 -30
  271. data/doc/TROUBLESHOOTING.md +0 -64
  272. data/doc/contributing/BUG_TRIAGE.md +0 -36
  273. data/doc/contributing/COMMUNITY.md +0 -13
  274. data/doc/contributing/GETTING_HELP.md +0 -11
  275. data/doc/contributing/HOW_YOU_CAN_HELP.md +0 -27
  276. data/doc/contributing/ISSUES.md +0 -51
  277. data/doc/contributing/README.md +0 -38
  278. data/doc/development/NEW_FEATURES.md +0 -10
  279. data/doc/development/PULL_REQUESTS.md +0 -40
  280. data/doc/development/README.md +0 -19
  281. data/doc/development/RELEASING.md +0 -9
  282. data/doc/development/SETUP.md +0 -27
  283. data/doc/documentation/README.md +0 -29
  284. data/doc/documentation/VISION.md +0 -26
  285. data/doc/documentation/WRITING.md +0 -54
  286. data/task/release.rake +0 -116
@@ -2,77 +2,81 @@ BUNDLE-OUTDATED(1) BUNDLE-OUTDATED(1)
2
2
 
3
3
 
4
4
 
5
- 1mNAME0m
6
- 1mbundle-outdated 22m- List installed gems with newer versions available
5
+ NAME
6
+ bundle-outdated - List installed gems with newer versions available
7
7
 
8
- 1mSYNOPSIS0m
9
- 1mbundle outdated 22m[GEM] [--local] [--pre] [--source] [--strict]
8
+ SYNOPSIS
9
+ bundle outdated [GEM] [--local] [--pre] [--source] [--strict]
10
10
  [--parseable | --porcelain] [--group=GROUP] [--groups]
11
11
  [--update-strict] [--patch|--minor|--major] [--filter-major] [--fil-
12
- ter-minor] [--filter-patch]
12
+ ter-minor] [--filter-patch] [--only-explicit]
13
13
 
14
- 1mDESCRIPTION0m
14
+ DESCRIPTION
15
15
  Outdated lists the names and versions of gems that have a newer version
16
16
  available in the given source. Calling outdated with [GEM [GEM]] will
17
17
  only check for newer versions of the given gems. Prerelease gems are
18
18
  ignored by default. If your gems are up to date, Bundler will exit with
19
19
  a status of 0. Otherwise, it will exit 1.
20
20
 
21
- 1mOPTIONS0m
22
- 1m--local0m
21
+ OPTIONS
22
+ --local
23
23
  Do not attempt to fetch gems remotely and use the gem cache
24
24
  instead.
25
25
 
26
- 1m--pre 22mCheck for newer pre-release gems.
26
+ --pre Check for newer pre-release gems.
27
27
 
28
- 1m--source0m
28
+ --source
29
29
  Check against a specific source.
30
30
 
31
- 1m--strict0m
31
+ --strict
32
32
  Only list newer versions allowed by your Gemfile requirements.
33
33
 
34
- 1m--parseable0m
34
+ --parseable, --porcelain
35
35
  Use minimal formatting for more parseable output.
36
36
 
37
- 1m--group0m
37
+ --group
38
38
  List gems from a specific group.
39
39
 
40
- 1m--groups0m
40
+ --groups
41
41
  List gems organized by groups.
42
42
 
43
- 1m--update-strict0m
43
+ --update-strict
44
44
  Strict conservative resolution, do not allow any gem to be
45
45
  updated past latest --patch | --minor| --major.
46
46
 
47
- 1m--minor0m
47
+ --minor
48
48
  Prefer updating only to next minor version.
49
49
 
50
- 1m--major0m
50
+ --major
51
51
  Prefer updating to next major version (default).
52
52
 
53
- 1m--patch0m
53
+ --patch
54
54
  Prefer updating only to next patch version.
55
55
 
56
- 1m--filter-major0m
56
+ --filter-major
57
57
  Only list major newer versions.
58
58
 
59
- 1m--filter-minor0m
59
+ --filter-minor
60
60
  Only list minor newer versions.
61
61
 
62
- 1m--filter-patch0m
62
+ --filter-patch
63
63
  Only list patch newer versions.
64
64
 
65
- 1mPATCH LEVEL OPTIONS0m
66
- See bundle update(1) 4mbundle-update.1.html24m for details.
65
+ --only-explicit
66
+ Only list gems specified in your Gemfile, not their dependen-
67
+ cies.
67
68
 
68
- One difference between the patch level options in 1mbundle update 22mand
69
- here is the 1m--strict 22moption. 1m--strict 22mwas already an option on outdated
70
- before the patch level options were added. 1m--strict 22mwasn't altered, and
71
- the 1m--update-strict 22moption on 1moutdated 22mreflects what 1m--strict 22mdoes on
72
- 1mbundle update22m.
69
+ PATCH LEVEL OPTIONS
70
+ See bundle update(1) bundle-update.1.html for details.
73
71
 
74
- 1mFILTERING OUTPUT0m
75
- The 3 filtering options do not affect the resolution of versions,
72
+ One difference between the patch level options in bundle update and
73
+ here is the --strict option. --strict was already an option on outdated
74
+ before the patch level options were added. --strict wasn't altered, and
75
+ the --update-strict option on outdated reflects what --strict does on
76
+ bundle update.
77
+
78
+ FILTERING OUTPUT
79
+ The 3 filtering options do not affect the resolution of versions,
76
80
  merely what versions are shown in the output.
77
81
 
78
82
  If the regular output shows the following:
@@ -85,7 +89,7 @@ BUNDLE-OUTDATED(1) BUNDLE-OUTDATED(1)
85
89
 
86
90
 
87
91
 
88
- 1m--filter-major 22mwould only show:
92
+ --filter-major would only show:
89
93
 
90
94
 
91
95
 
@@ -93,7 +97,7 @@ BUNDLE-OUTDATED(1) BUNDLE-OUTDATED(1)
93
97
 
94
98
 
95
99
 
96
- 1m--filter-minor 22mwould only show:
100
+ --filter-minor would only show:
97
101
 
98
102
 
99
103
 
@@ -101,7 +105,7 @@ BUNDLE-OUTDATED(1) BUNDLE-OUTDATED(1)
101
105
 
102
106
 
103
107
 
104
- 1m--filter-patch 22mwould only show:
108
+ --filter-patch would only show:
105
109
 
106
110
 
107
111
 
@@ -109,7 +113,7 @@ BUNDLE-OUTDATED(1) BUNDLE-OUTDATED(1)
109
113
 
110
114
 
111
115
 
112
- Filter options can be combined. 1m--filter-minor 22mand 1m--filter-patch 22mwould
116
+ Filter options can be combined. --filter-minor and --filter-patch would
113
117
  show:
114
118
 
115
119
 
@@ -119,9 +123,9 @@ BUNDLE-OUTDATED(1) BUNDLE-OUTDATED(1)
119
123
 
120
124
 
121
125
 
122
- Combining all three 1mfilter 22moptions would be the same result as provid-
126
+ Combining all three filter options would be the same result as provid-
123
127
  ing none of them.
124
128
 
125
129
 
126
130
 
127
- June 2017 BUNDLE-OUTDATED(1)
131
+ December 2018 BUNDLE-OUTDATED(1)
@@ -15,6 +15,7 @@ bundle-outdated(1) -- List installed gems with newer versions available
15
15
  [--filter-major]
16
16
  [--filter-minor]
17
17
  [--filter-patch]
18
+ [--only-explicit]
18
19
 
19
20
  ## DESCRIPTION
20
21
 
@@ -37,7 +38,7 @@ are up to date, Bundler will exit with a status of 0. Otherwise, it will exit 1.
37
38
  * `--strict`:
38
39
  Only list newer versions allowed by your Gemfile requirements.
39
40
 
40
- * `--parseable`:
41
+ * `--parseable`, `--porcelain`:
41
42
  Use minimal formatting for more parseable output.
42
43
 
43
44
  * `--group`:
@@ -67,9 +68,12 @@ are up to date, Bundler will exit with a status of 0. Otherwise, it will exit 1.
67
68
  * `--filter-patch`:
68
69
  Only list patch newer versions.
69
70
 
71
+ * `--only-explicit`:
72
+ Only list gems specified in your Gemfile, not their dependencies.
73
+
70
74
  ## PATCH LEVEL OPTIONS
71
75
 
72
- See [bundle update(1)][bundle-update] for details.
76
+ See [bundle update(1)](bundle-update.1.html) for details.
73
77
 
74
78
  One difference between the patch level options in `bundle update` and here is the `--strict` option.
75
79
  `--strict` was already an option on outdated before the patch level options were added. `--strict`
data/man/bundle-package.1 CHANGED
@@ -1,7 +1,7 @@
1
1
  .\" generated with Ronn/v0.7.3
2
2
  .\" http://github.com/rtomayko/ronn/tree/0.7.3
3
3
  .
4
- .TH "BUNDLE\-PACKAGE" "1" "June 2017" "" ""
4
+ .TH "BUNDLE\-PACKAGE" "1" "November 2018" "" ""
5
5
  .
6
6
  .SH "NAME"
7
7
  \fBbundle\-package\fR \- Package your needed \fB\.gem\fR files into your application
@@ -10,7 +10,7 @@
10
10
  \fBbundle package\fR
11
11
  .
12
12
  .SH "DESCRIPTION"
13
- Copy all of the \fB\.gem\fR files needed to run the application into the \fBvendor/cache\fR directory\. In the future, when running bundle install(1) \fIbundle\-install\.1\.html\fR, use the gems in the cache in preference to the ones on \fBrubygems\.org\fR\.
13
+ Copy all of the \fB\.gem\fR files needed to run the application into the \fBvendor/cache\fR directory\. In the future, when running [bundle install(1)][bundle\-install], use the gems in the cache in preference to the ones on \fBrubygems\.org\fR\.
14
14
  .
15
15
  .SH "GIT AND PATH GEMS"
16
16
  Since Bundler 1\.2, the \fBbundle package\fR command can also package \fB:git\fR and \fB:path\fR dependencies besides \.gem files\. This needs to be explicitly enabled via the \fB\-\-all\fR option\. Once used, the \fB\-\-all\fR option will be remembered\.
@@ -19,7 +19,7 @@ Since Bundler 1\.2, the \fBbundle package\fR command can also package \fB:git\fR
19
19
  When using gems that have different packages for different platforms, Bundler 1\.8 and newer support caching of gems for other platforms where the Gemfile has been resolved (i\.e\. present in the lockfile) in \fBvendor/cache\fR\. This needs to be enabled via the \fB\-\-all\-platforms\fR option\. This setting will be remembered in your local bundler configuration\.
20
20
  .
21
21
  .SH "REMOTE FETCHING"
22
- By default, if you run bundle install(1) \fIbundle\-install\.1\.html\fR after running bundle package(1) \fIbundle\-package\.1\.html\fR, bundler will still connect to \fBrubygems\.org\fR to check whether a platform\-specific gem exists for any of the gems in \fBvendor/cache\fR\.
22
+ By default, if you run \fBbundle install(1)\fR](bundle\-install\.1\.html) after running bundle package(1) \fIbundle\-package\.1\.html\fR, bundler will still connect to \fBrubygems\.org\fR to check whether a platform\-specific gem exists for any of the gems in \fBvendor/cache\fR\.
23
23
  .
24
24
  .P
25
25
  For instance, consider this Gemfile(5):
@@ -50,3 +50,6 @@ If you know for sure that the gems packaged in \fBvendor/cache\fR are appropriat
50
50
  .
51
51
  .P
52
52
  One way to be sure that you have the right platformed versions of all your gems is to run \fBbundle package\fR on an identical machine and check in the gems\. For instance, you can run \fBbundle package\fR on an identical staging box during your staging process, and check in the \fBvendor/cache\fR before deploying to production\.
53
+ .
54
+ .P
55
+ By default, bundle package(1) \fIbundle\-package\.1\.html\fR fetches and also installs the gems to the default location\. To package the dependencies to \fBvendor/cache\fR without installing them to the local install location, you can run \fBbundle package \-\-no\-install\fR\.
@@ -2,36 +2,36 @@ BUNDLE-PACKAGE(1) BUNDLE-PACKAGE(1)
2
2
 
3
3
 
4
4
 
5
- 1mNAME0m
6
- 1mbundle-package 22m- Package your needed 1m.gem 22mfiles into your application
7
-
8
- 1mSYNOPSIS0m
9
- 1mbundle package0m
10
-
11
- 1mDESCRIPTION0m
12
- Copy all of the 1m.gem 22mfiles needed to run the application into the 1mven-0m
13
- 1mdor/cache 22mdirectory. In the future, when running bundle install(1) 4mbun-0m
14
- 4mdle-install.1.html24m, use the gems in the cache in preference to the ones
15
- on 1mrubygems.org22m.
16
-
17
- 1mGIT AND PATH GEMS0m
18
- Since Bundler 1.2, the 1mbundle package 22mcommand can also package 1m:git 22mand
19
- 1m:path 22mdependencies besides .gem files. This needs to be explicitly
20
- enabled via the 1m--all 22moption. Once used, the 1m--all 22moption will be
5
+ NAME
6
+ bundle-package - Package your needed .gem files into your application
7
+
8
+ SYNOPSIS
9
+ bundle package
10
+
11
+ DESCRIPTION
12
+ Copy all of the .gem files needed to run the application into the ven-
13
+ dor/cache directory. In the future, when running [bundle
14
+ install(1)][bundle-install], use the gems in the cache in preference to
15
+ the ones on rubygems.org.
16
+
17
+ GIT AND PATH GEMS
18
+ Since Bundler 1.2, the bundle package command can also package :git and
19
+ :path dependencies besides .gem files. This needs to be explicitly
20
+ enabled via the --all option. Once used, the --all option will be
21
21
  remembered.
22
22
 
23
- 1mSUPPORT FOR MULTIPLE PLATFORMS0m
23
+ SUPPORT FOR MULTIPLE PLATFORMS
24
24
  When using gems that have different packages for different platforms,
25
25
  Bundler 1.8 and newer support caching of gems for other platforms where
26
- the Gemfile has been resolved (i.e. present in the lockfile) in 1mven-0m
27
- 1mdor/cache22m. This needs to be enabled via the 1m--all-platforms 22moption.
26
+ the Gemfile has been resolved (i.e. present in the lockfile) in ven-
27
+ dor/cache. This needs to be enabled via the --all-platforms option.
28
28
  This setting will be remembered in your local bundler configuration.
29
29
 
30
- 1mREMOTE FETCHING0m
31
- By default, if you run bundle install(1) 4mbundle-install.1.html24m after
32
- running bundle package(1) 4mbundle-package.1.html24m, bundler will still
33
- connect to 1mrubygems.org 22mto check whether a platform-specific gem exists
34
- for any of the gems in 1mvendor/cache22m.
30
+ REMOTE FETCHING
31
+ By default, if you run bundle install(1)](bundle-install.1.html) after
32
+ running bundle package(1) bundle-package.1.html, bundler will still
33
+ connect to rubygems.org to check whether a platform-specific gem exists
34
+ for any of the gems in vendor/cache.
35
35
 
36
36
  For instance, consider this Gemfile(5):
37
37
 
@@ -43,32 +43,37 @@ BUNDLE-PACKAGE(1) BUNDLE-PACKAGE(1)
43
43
 
44
44
 
45
45
 
46
- If you run 1mbundle package 22munder C Ruby, bundler will retrieve the ver-
47
- sion of 1mnokogiri 22mfor the 1m"ruby" 22mplatform. If you deploy to JRuby and
48
- run 1mbundle install22m, bundler is forced to check to see whether a 1m"java"0m
49
- platformed 1mnokogiri 22mexists.
46
+ If you run bundle package under C Ruby, bundler will retrieve the ver-
47
+ sion of nokogiri for the "ruby" platform. If you deploy to JRuby and
48
+ run bundle install, bundler is forced to check to see whether a "java"
49
+ platformed nokogiri exists.
50
50
 
51
- Even though the 1mnokogiri 22mgem for the Ruby platform is 4mtechnically0m
51
+ Even though the nokogiri gem for the Ruby platform is technically
52
52
  acceptable on JRuby, it has a C extension that does not run on JRuby.
53
- As a result, bundler will, by default, still connect to 1mrubygems.org 22mto
53
+ As a result, bundler will, by default, still connect to rubygems.org to
54
54
  check whether it has a version of one of your gems more specific to
55
55
  your platform.
56
56
 
57
- This problem is also not limited to the 1m"java" 22mplatform. A similar
57
+ This problem is also not limited to the "java" platform. A similar
58
58
  (common) problem can happen when developing on Windows and deploying to
59
59
  Linux, or even when developing on OSX and deploying to Linux.
60
60
 
61
- If you know for sure that the gems packaged in 1mvendor/cache 22mare appro-
62
- priate for the platform you are on, you can run 1mbundle install --local0m
63
- to skip checking for more appropriate gems, and use the ones in 1mven-0m
64
- 1mdor/cache22m.
61
+ If you know for sure that the gems packaged in vendor/cache are appro-
62
+ priate for the platform you are on, you can run bundle install --local
63
+ to skip checking for more appropriate gems, and use the ones in ven-
64
+ dor/cache.
65
65
 
66
66
  One way to be sure that you have the right platformed versions of all
67
- your gems is to run 1mbundle package 22mon an identical machine and check in
68
- the gems. For instance, you can run 1mbundle package 22mon an identical
69
- staging box during your staging process, and check in the 1mvendor/cache0m
67
+ your gems is to run bundle package on an identical machine and check in
68
+ the gems. For instance, you can run bundle package on an identical
69
+ staging box during your staging process, and check in the vendor/cache
70
70
  before deploying to production.
71
71
 
72
+ By default, bundle package(1) bundle-package.1.html fetches and also
73
+ installs the gems to the default location. To package the dependencies
74
+ to vendor/cache without installing them to the local install location,
75
+ you can run bundle package --no-install.
72
76
 
73
77
 
74
- June 2017 BUNDLE-PACKAGE(1)
78
+
79
+ November 2018 BUNDLE-PACKAGE(1)
@@ -27,8 +27,8 @@ in your local bundler configuration.
27
27
 
28
28
  ## REMOTE FETCHING
29
29
 
30
- By default, if you run [bundle install(1)][bundle-install] after running
31
- [bundle package(1)][bundle-package], bundler will still connect to `rubygems.org`
30
+ By default, if you run `bundle install(1)`](bundle-install.1.html) after running
31
+ [bundle package(1)](bundle-package.1.html), bundler will still connect to `rubygems.org`
32
32
  to check whether a platform-specific gem exists for any of the gems
33
33
  in `vendor/cache`.
34
34
 
@@ -65,3 +65,8 @@ machine and check in the gems. For instance, you can run
65
65
  `bundle package` on an identical staging box during your
66
66
  staging process, and check in the `vendor/cache` before
67
67
  deploying to production.
68
+
69
+ By default, [bundle package(1)](bundle-package.1.html) fetches and also
70
+ installs the gems to the default location. To package the
71
+ dependencies to `vendor/cache` without installing them to the
72
+ local install location, you can run `bundle package --no-install`.
@@ -1,7 +1,7 @@
1
1
  .\" generated with Ronn/v0.7.3
2
2
  .\" http://github.com/rtomayko/ronn/tree/0.7.3
3
3
  .
4
- .TH "BUNDLE\-PLATFORM" "1" "June 2017" "" ""
4
+ .TH "BUNDLE\-PLATFORM" "1" "November 2018" "" ""
5
5
  .
6
6
  .SH "NAME"
7
7
  \fBbundle\-platform\fR \- Displays platform compatibility information
@@ -2,14 +2,14 @@ BUNDLE-PLATFORM(1) BUNDLE-PLATFORM(1)
2
2
 
3
3
 
4
4
 
5
- 1mNAME0m
6
- 1mbundle-platform 22m- Displays platform compatibility information
5
+ NAME
6
+ bundle-platform - Displays platform compatibility information
7
7
 
8
- 1mSYNOPSIS0m
9
- 1mbundle platform 22m[--ruby]
8
+ SYNOPSIS
9
+ bundle platform [--ruby]
10
10
 
11
- 1mDESCRIPTION0m
12
- 1mplatform 22mwill display information from your Gemfile, Gemfile.lock, and
11
+ DESCRIPTION
12
+ platform will display information from your Gemfile, Gemfile.lock, and
13
13
  Ruby VM about your platform.
14
14
 
15
15
  For instance, using this Gemfile(5):
@@ -24,7 +24,7 @@ BUNDLE-PLATFORM(1) BUNDLE-PLATFORM(1)
24
24
 
25
25
 
26
26
 
27
- If you run 1mbundle platform 22mon Ruby 1.9.3, it will display the following
27
+ If you run bundle platform on Ruby 1.9.3, it will display the following
28
28
  output:
29
29
 
30
30
 
@@ -41,17 +41,17 @@ BUNDLE-PLATFORM(1) BUNDLE-PLATFORM(1)
41
41
 
42
42
 
43
43
 
44
- 1mplatform 22mwill list all the platforms in your 1mGemfile.lock 22mas well as
45
- the 1mruby 22mdirective if applicable from your Gemfile(5). It will also let
46
- you know if the 1mruby 22mdirective requirement has been met. If 1mruby 22mdirec-
44
+ platform will list all the platforms in your Gemfile.lock as well as
45
+ the ruby directive if applicable from your Gemfile(5). It will also let
46
+ you know if the ruby directive requirement has been met. If ruby direc-
47
47
  tive doesn't match the running Ruby VM, it will tell you what part does
48
48
  not.
49
49
 
50
- 1mOPTIONS0m
51
- 1m--ruby 22mIt will display the ruby directive information, so you don't
50
+ OPTIONS
51
+ --ruby It will display the ruby directive information, so you don't
52
52
  have to parse it from the Gemfile(5).
53
53
 
54
54
 
55
55
 
56
56
 
57
- June 2017 BUNDLE-PLATFORM(1)
57
+ November 2018 BUNDLE-PLATFORM(1)
@@ -1,7 +1,7 @@
1
1
  .\" generated with Ronn/v0.7.3
2
2
  .\" http://github.com/rtomayko/ronn/tree/0.7.3
3
3
  .
4
- .TH "BUNDLE\-PRISTINE" "1" "June 2017" "" ""
4
+ .TH "BUNDLE\-PRISTINE" "1" "November 2018" "" ""
5
5
  .
6
6
  .SH "NAME"
7
7
  \fBbundle\-pristine\fR \- Restores installed gems to their pristine condition
@@ -10,7 +10,25 @@
10
10
  \fBbundle pristine\fR
11
11
  .
12
12
  .SH "DESCRIPTION"
13
- \fBpristine\fR restores the installed gems in the bundle to their pristine condition using the local gem cache from RubyGems\. For git gems \- a forced checkout will be performed\.
13
+ \fBpristine\fR restores the installed gems in the bundle to their pristine condition using the local gem cache from RubyGems\. For git gems, a forced checkout will be performed\.
14
14
  .
15
15
  .P
16
- Note the Bundler gem cannot be restored to its original state with \fBpristine\fR\.
16
+ For further explanation, \fBbundle pristine\fR ignores unpacked files on disk\. In other words, this command utilizes the local \fB\.gem\fR cache or the gem\'s git repository as if one were installing from scratch\.
17
+ .
18
+ .P
19
+ Note: the Bundler gem cannot be restored to its original state with \fBpristine\fR\. One also cannot use \fBbundle pristine\fR on gems with a \'path\' option in the Gemfile, because bundler has no original copy it can restore from\.
20
+ .
21
+ .P
22
+ When is it practical to use \fBbundle pristine\fR?
23
+ .
24
+ .P
25
+ It comes in handy when a developer is debugging a gem\. \fBbundle pristine\fR is a great way to get rid of experimental changes to a gem that one may not want\.
26
+ .
27
+ .P
28
+ Why use \fBbundle pristine\fR over \fBgem pristine \-\-all\fR?
29
+ .
30
+ .P
31
+ Both commands are very similar\. For context: \fBbundle pristine\fR, without arguments, cleans all gems from the lockfile\. Meanwhile, \fBgem pristine \-\-all\fR cleans all installed gems for that Ruby version\.
32
+ .
33
+ .P
34
+ If a developer forgets which gems in their project they might have been debugging, the Rubygems \fBgem pristine [GEMNAME]\fR command may be inconvenient\. One can avoid waiting for \fBgem pristine \-\-all\fR, and instead run \fBbundle pristine\fR\.
@@ -2,20 +2,43 @@ BUNDLE-PRISTINE(1) BUNDLE-PRISTINE(1)
2
2
 
3
3
 
4
4
 
5
- 1mNAME0m
6
- 1mbundle-pristine 22m- Restores installed gems to their pristine condition
5
+ NAME
6
+ bundle-pristine - Restores installed gems to their pristine condition
7
7
 
8
- 1mSYNOPSIS0m
9
- 1mbundle pristine0m
8
+ SYNOPSIS
9
+ bundle pristine
10
10
 
11
- 1mDESCRIPTION0m
12
- 1mpristine 22mrestores the installed gems in the bundle to their pristine
13
- condition using the local gem cache from RubyGems. For git gems - a
11
+ DESCRIPTION
12
+ pristine restores the installed gems in the bundle to their pristine
13
+ condition using the local gem cache from RubyGems. For git gems, a
14
14
  forced checkout will be performed.
15
15
 
16
- Note the Bundler gem cannot be restored to its original state with
17
- 1mpristine22m.
16
+ For further explanation, bundle pristine ignores unpacked files on
17
+ disk. In other words, this command utilizes the local .gem cache or the
18
+ gem's git repository as if one were installing from scratch.
18
19
 
20
+ Note: the Bundler gem cannot be restored to its original state with
21
+ pristine. One also cannot use bundle pristine on gems with a 'path'
22
+ option in the Gemfile, because bundler has no original copy it can
23
+ restore from.
19
24
 
25
+ When is it practical to use bundle pristine?
20
26
 
21
- June 2017 BUNDLE-PRISTINE(1)
27
+ It comes in handy when a developer is debugging a gem. bundle pristine
28
+ is a great way to get rid of experimental changes to a gem that one may
29
+ not want.
30
+
31
+ Why use bundle pristine over gem pristine --all?
32
+
33
+ Both commands are very similar. For context: bundle pristine, without
34
+ arguments, cleans all gems from the lockfile. Meanwhile, gem pristine
35
+ --all cleans all installed gems for that Ruby version.
36
+
37
+ If a developer forgets which gems in their project they might have been
38
+ debugging, the Rubygems gem pristine [GEMNAME] command may be inconve-
39
+ nient. One can avoid waiting for gem pristine --all, and instead run
40
+ bundle pristine.
41
+
42
+
43
+
44
+ November 2018 BUNDLE-PRISTINE(1)
@@ -7,7 +7,28 @@ bundle-pristine(1) -- Restores installed gems to their pristine condition
7
7
 
8
8
  ## DESCRIPTION
9
9
 
10
- `pristine` restores the installed gems in the bundle to their pristine condition using the local gem
11
- cache from RubyGems. For git gems - a forced checkout will be performed.
10
+ `pristine` restores the installed gems in the bundle to their pristine condition
11
+ using the local gem cache from RubyGems. For git gems, a forced checkout will be performed.
12
12
 
13
- Note the Bundler gem cannot be restored to its original state with `pristine`.
13
+ For further explanation, `bundle pristine` ignores unpacked files on disk. In other
14
+ words, this command utilizes the local `.gem` cache or the gem's git repository
15
+ as if one were installing from scratch.
16
+
17
+ Note: the Bundler gem cannot be restored to its original state with `pristine`.
18
+ One also cannot use `bundle pristine` on gems with a 'path' option in the Gemfile,
19
+ because bundler has no original copy it can restore from.
20
+
21
+ When is it practical to use `bundle pristine`?
22
+
23
+ It comes in handy when a developer is debugging a gem. `bundle pristine` is a
24
+ great way to get rid of experimental changes to a gem that one may not want.
25
+
26
+ Why use `bundle pristine` over `gem pristine --all`?
27
+
28
+ Both commands are very similar.
29
+ For context: `bundle pristine`, without arguments, cleans all gems from the lockfile.
30
+ Meanwhile, `gem pristine --all` cleans all installed gems for that Ruby version.
31
+
32
+ If a developer forgets which gems in their project they might
33
+ have been debugging, the Rubygems `gem pristine [GEMNAME]` command may be inconvenient.
34
+ One can avoid waiting for `gem pristine --all`, and instead run `bundle pristine`.
@@ -0,0 +1,31 @@
1
+ .\" generated with Ronn/v0.7.3
2
+ .\" http://github.com/rtomayko/ronn/tree/0.7.3
3
+ .
4
+ .TH "BUNDLE\-REMOVE" "1" "December 2018" "" ""
5
+ .
6
+ .SH "NAME"
7
+ \fBbundle\-remove\fR \- Removes gems from the Gemfile
8
+ .
9
+ .SH "SYNOPSIS"
10
+ \fBbundle remove [GEM [GEM \.\.\.]] [\-\-install]\fR
11
+ .
12
+ .SH "DESCRIPTION"
13
+ Removes the given gems from the Gemfile while ensuring that the resulting Gemfile is still valid\. If a gem cannot be removed, a warning is printed\. If a gem is already absent from the Gemfile, and error is raised\.
14
+ .
15
+ .SH "OPTIONS"
16
+ .
17
+ .TP
18
+ \fB\-\-install\fR
19
+ Runs \fBbundle install\fR after the given gems have been removed from the Gemfile, which ensures that both the lockfile and the installed gems on disk are also updated to remove the given gem(s)\.
20
+ .
21
+ .P
22
+ Example:
23
+ .
24
+ .P
25
+ bundle remove rails
26
+ .
27
+ .P
28
+ bundle remove rails rack
29
+ .
30
+ .P
31
+ bundle remove rails rack \-\-install
@@ -0,0 +1,34 @@
1
+ BUNDLE-REMOVE(1) BUNDLE-REMOVE(1)
2
+
3
+
4
+
5
+ NAME
6
+ bundle-remove - Removes gems from the Gemfile
7
+
8
+ SYNOPSIS
9
+ bundle remove [GEM [GEM ...]] [--install]
10
+
11
+ DESCRIPTION
12
+ Removes the given gems from the Gemfile while ensuring that the result-
13
+ ing Gemfile is still valid. If a gem cannot be removed, a warning is
14
+ printed. If a gem is already absent from the Gemfile, and error is
15
+ raised.
16
+
17
+ OPTIONS
18
+ --install
19
+ Runs bundle install after the given gems have been removed from
20
+ the Gemfile, which ensures that both the lockfile and the
21
+ installed gems on disk are also updated to remove the given
22
+ gem(s).
23
+
24
+ Example:
25
+
26
+ bundle remove rails
27
+
28
+ bundle remove rails rack
29
+
30
+ bundle remove rails rack --install
31
+
32
+
33
+
34
+ December 2018 BUNDLE-REMOVE(1)
@@ -0,0 +1,23 @@
1
+ bundle-remove(1) -- Removes gems from the Gemfile
2
+ ===========================================================================
3
+
4
+ ## SYNOPSIS
5
+
6
+ `bundle remove [GEM [GEM ...]] [--install]`
7
+
8
+ ## DESCRIPTION
9
+
10
+ Removes the given gems from the Gemfile while ensuring that the resulting Gemfile is still valid. If a gem cannot be removed, a warning is printed. If a gem is already absent from the Gemfile, and error is raised.
11
+
12
+ ## OPTIONS
13
+
14
+ * `--install`:
15
+ Runs `bundle install` after the given gems have been removed from the Gemfile, which ensures that both the lockfile and the installed gems on disk are also updated to remove the given gem(s).
16
+
17
+ Example:
18
+
19
+ bundle remove rails
20
+
21
+ bundle remove rails rack
22
+
23
+ bundle remove rails rack --install