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,53 +2,53 @@ BUNDLE-EXEC(1) BUNDLE-EXEC(1)
2
2
 
3
3
 
4
4
 
5
- 1mNAME0m
6
- 1mbundle-exec 22m- Execute a command in the context of the bundle
5
+ NAME
6
+ bundle-exec - Execute a command in the context of the bundle
7
7
 
8
- 1mSYNOPSIS0m
9
- 1mbundle exec 22m[--keep-file-descriptors] 4mcommand0m
8
+ SYNOPSIS
9
+ bundle exec [--keep-file-descriptors] command
10
10
 
11
- 1mDESCRIPTION0m
11
+ DESCRIPTION
12
12
  This command executes the command, making all gems specified in the
13
- 1mGemfile(5) 22mavailable to 1mrequire 22min Ruby programs.
13
+ [Gemfile(5)][Gemfile(5)] available to require in Ruby programs.
14
14
 
15
- Essentially, if you would normally have run something like 1mrspec0m
16
- 1mspec/my_spec.rb22m, and you want to use the gems specified in the 1mGem-0m
17
- 1mfile(5) 22mand installed via bundle install(1) 4mbundle-install.1.html24m, you
18
- should run 1mbundle exec rspec spec/my_spec.rb22m.
15
+ Essentially, if you would normally have run something like rspec
16
+ spec/my_spec.rb, and you want to use the gems specified in the [Gem-
17
+ file(5)][Gemfile(5)] and installed via bundle install(1) bun-
18
+ dle-install.1.html, you should run bundle exec rspec spec/my_spec.rb.
19
19
 
20
- Note that 1mbundle exec 22mdoes not require that an executable is available
21
- on your shell's 1m$PATH22m.
20
+ Note that bundle exec does not require that an executable is available
21
+ on your shell's $PATH.
22
22
 
23
- 1mOPTIONS0m
24
- 1m--keep-file-descriptors0m
23
+ OPTIONS
24
+ --keep-file-descriptors
25
25
  Exec in Ruby 2.0 began discarding non-standard file descriptors.
26
26
  When this flag is passed, exec will revert to the 1.9 behaviour
27
27
  of passing all file descriptors to the new process.
28
28
 
29
- 1mBUNDLE INSTALL --BINSTUBS0m
30
- If you use the 1m--binstubs 22mflag in bundle install(1) 4mbun-0m
31
- 4mdle-install.1.html24m, Bundler will automatically create a directory
32
- (which defaults to 1mapp_root/bin22m) containing all of the executables
29
+ BUNDLE INSTALL --BINSTUBS
30
+ If you use the --binstubs flag in bundle install(1) bun-
31
+ dle-install.1.html, Bundler will automatically create a directory
32
+ (which defaults to app_root/bin) containing all of the executables
33
33
  available from gems in the bundle.
34
34
 
35
- After using 1m--binstubs22m, 1mbin/rspec spec/my_spec.rb 22mis identical to 1mbun-0m
36
- 1mdle exec rspec spec/my_spec.rb22m.
35
+ After using --binstubs, bin/rspec spec/my_spec.rb is identical to bun-
36
+ dle exec rspec spec/my_spec.rb.
37
37
 
38
- 1mENVIRONMENT MODIFICATIONS0m
39
- 1mbundle exec 22mmakes a number of changes to the shell environment, then
38
+ ENVIRONMENT MODIFICATIONS
39
+ bundle exec makes a number of changes to the shell environment, then
40
40
  executes the command you specify in full.
41
41
 
42
- o make sure that it's still possible to shell out to 1mbundle 22mfrom
43
- inside a command invoked by 1mbundle exec 22m(using 1m$BUNDLE_BIN_PATH22m)
42
+ o make sure that it's still possible to shell out to bundle from
43
+ inside a command invoked by bundle exec (using $BUNDLE_BIN_PATH)
44
44
 
45
- o put the directory containing executables (like 1mrails22m, 1mrspec22m,
46
- 1mrackup22m) for your bundle on 1m$PATH0m
45
+ o put the directory containing executables (like rails, rspec,
46
+ rackup) for your bundle on $PATH
47
47
 
48
48
  o make sure that if bundler is invoked in the subshell, it uses the
49
- same 1mGemfile 22m(by setting 1mBUNDLE_GEMFILE22m)
49
+ same Gemfile (by setting BUNDLE_GEMFILE)
50
50
 
51
- o add 1m-rbundler/setup 22mto 1m$RUBYOPT22m, which makes sure that Ruby pro-
51
+ o add -rbundler/setup to $RUBYOPT, which makes sure that Ruby pro-
52
52
  grams invoked in the subshell can see the gems in the bundle
53
53
 
54
54
 
@@ -57,35 +57,42 @@ BUNDLE-EXEC(1) BUNDLE-EXEC(1)
57
57
 
58
58
  o disallow loading additional gems not in the bundle
59
59
 
60
- o modify the 1mgem 22mmethod to be a no-op if a gem matching the require-
61
- ments is in the bundle, and to raise a 1mGem::LoadError 22mif it's not
60
+ o modify the gem method to be a no-op if a gem matching the require-
61
+ ments is in the bundle, and to raise a Gem::LoadError if it's not
62
62
 
63
- o Define 1mGem.refresh 22mto be a no-op, since the source index is always
63
+ o Define Gem.refresh to be a no-op, since the source index is always
64
64
  frozen when using bundler, and to prevent gems from the system
65
65
  leaking into the environment
66
66
 
67
- o Override 1mGem.bin_path 22mto use the gems in the bundle, making system
67
+ o Override Gem.bin_path to use the gems in the bundle, making system
68
68
  executables work
69
69
 
70
70
  o Add all gems in the bundle into Gem.loaded_specs
71
71
 
72
72
 
73
73
 
74
- 1mLoading0m
75
- By default, when attempting to 1mbundle exec 22mto a file with a ruby she-
76
- bang, Bundler will 1mKernel.load 22mthat file instead of using 1mKernel.exec22m.
74
+ Finally, bundle exec also implicitly modifies Gemfile.lock if the lock-
75
+ file and the Gemfile do not match. Bundler needs the Gemfile to deter-
76
+ mine things such as a gem's groups, autorequire, and platforms, etc.,
77
+ and that information isn't stored in the lockfile. The Gemfile and
78
+ lockfile must be synced in order to bundle exec successfully, so bundle
79
+ exec updates the lockfile beforehand.
80
+
81
+ Loading
82
+ By default, when attempting to bundle exec to a file with a ruby she-
83
+ bang, Bundler will Kernel.load that file instead of using Kernel.exec.
77
84
  For the vast majority of cases, this is a performance improvement. In a
78
- rare few cases, this could cause some subtle side-effects (such as
79
- dependence on the exact contents of 1m$0 22mor 1m__FILE__22m) and the optimiza-
80
- tion can be disabled by enabling the 1mdisable_exec_load 22msetting.
81
-
82
- 1mShelling out0m
83
- Any Ruby code that opens a subshell (like 1msystem22m, backticks, or 1m%x{}22m)
84
- will automatically use the current Bundler environment. If you need to
85
- shell out to a Ruby command that is not part of your current bundle,
86
- use the 1mwith_clean_env 22mmethod with a block. Any subshells created
87
- inside the block will be given the environment present before Bundler
88
- was activated. For example, Homebrew commands run Ruby, but don't work
85
+ rare few cases, this could cause some subtle side-effects (such as
86
+ dependence on the exact contents of $0 or __FILE__) and the optimiza-
87
+ tion can be disabled by enabling the disable_exec_load setting.
88
+
89
+ Shelling out
90
+ Any Ruby code that opens a subshell (like system, backticks, or %x{})
91
+ will automatically use the current Bundler environment. If you need to
92
+ shell out to a Ruby command that is not part of your current bundle,
93
+ use the with_clean_env method with a block. Any subshells created
94
+ inside the block will be given the environment present before Bundler
95
+ was activated. For example, Homebrew commands run Ruby, but don't work
89
96
  inside a bundle:
90
97
 
91
98
 
@@ -96,10 +103,10 @@ BUNDLE-EXEC(1) BUNDLE-EXEC(1)
96
103
 
97
104
 
98
105
 
99
- Using 1mwith_clean_env 22mis also necessary if you are shelling out to a
100
- different bundle. Any Bundler commands run in a subshell will inherit
101
- the current Gemfile, so commands that need to run in the context of a
102
- different bundle also need to use 1mwith_clean_env22m.
106
+ Using with_clean_env is also necessary if you are shelling out to a
107
+ different bundle. Any Bundler commands run in a subshell will inherit
108
+ the current Gemfile, so commands that need to run in the context of a
109
+ different bundle also need to use with_clean_env.
103
110
 
104
111
 
105
112
 
@@ -111,7 +118,7 @@ BUNDLE-EXEC(1) BUNDLE-EXEC(1)
111
118
 
112
119
 
113
120
 
114
- Bundler provides convenience helpers that wrap 1msystem 22mand 1mexec22m, and
121
+ Bundler provides convenience helpers that wrap system and exec, and
115
122
  they can be used like this:
116
123
 
117
124
 
@@ -121,24 +128,24 @@ BUNDLE-EXEC(1) BUNDLE-EXEC(1)
121
128
 
122
129
 
123
130
 
124
- 1mRUBYGEMS PLUGINS0m
125
- At present, the Rubygems plugin system requires all files named
126
- 1mrubygems_plugin.rb 22mon the load path of 4many24m installed gem when any Ruby
127
- code requires 1mrubygems.rb22m. This includes executables installed into the
128
- system, like 1mrails22m, 1mrackup22m, and 1mrspec22m.
131
+ RUBYGEMS PLUGINS
132
+ At present, the Rubygems plugin system requires all files named
133
+ rubygems_plugin.rb on the load path of any installed gem when any Ruby
134
+ code requires rubygems.rb. This includes executables installed into the
135
+ system, like rails, rackup, and rspec.
129
136
 
130
- Since Rubygems plugins can contain arbitrary Ruby code, they commonly
137
+ Since Rubygems plugins can contain arbitrary Ruby code, they commonly
131
138
  end up activating themselves or their dependencies.
132
139
 
133
- For instance, the 1mgemcutter 0.5 22mgem depended on 1mjson_pure22m. If you had
134
- that version of gemcutter installed (even if you 4malso24m had a newer ver-
135
- sion without this problem), Rubygems would activate 1mgemcutter 0.5 22mand
136
- 1mjson_pure <latest>22m.
140
+ For instance, the gemcutter 0.5 gem depended on json_pure. If you had
141
+ that version of gemcutter installed (even if you also had a newer ver-
142
+ sion without this problem), Rubygems would activate gemcutter 0.5 and
143
+ json_pure <latest>.
137
144
 
138
- If your Gemfile(5) also contained 1mjson_pure 22m(or a gem with a dependency
139
- on 1mjson_pure22m), the latest version on your system might conflict with
140
- the version in your Gemfile(5), or the snapshot version in your 1mGem-0m
141
- 1mfile.lock22m.
145
+ If your Gemfile(5) also contained json_pure (or a gem with a dependency
146
+ on json_pure), the latest version on your system might conflict with
147
+ the version in your Gemfile(5), or the snapshot version in your Gem-
148
+ file.lock.
142
149
 
143
150
  If this happens, bundler will say:
144
151
 
@@ -149,9 +156,9 @@ BUNDLE-EXEC(1) BUNDLE-EXEC(1)
149
156
 
150
157
 
151
158
 
152
- In this situation, you almost certainly want to remove the underlying
153
- gem with the problematic gem plugin. In general, the authors of these
154
- plugins (in this case, the 1mgemcutter 22mgem) have released newer versions
159
+ In this situation, you almost certainly want to remove the underlying
160
+ gem with the problematic gem plugin. In general, the authors of these
161
+ plugins (in this case, the gemcutter gem) have released newer versions
155
162
  that are more careful in their plugins.
156
163
 
157
164
  You can find a list of all the gems containing gem plugins by running
@@ -163,9 +170,9 @@ BUNDLE-EXEC(1) BUNDLE-EXEC(1)
163
170
 
164
171
 
165
172
  At the very least, you should remove all but the newest version of each
166
- gem plugin, and also remove all gem plugins that you aren't using (1mgem0m
167
- 1muninstall gem_name22m).
173
+ gem plugin, and also remove all gem plugins that you aren't using (gem
174
+ uninstall gem_name).
168
175
 
169
176
 
170
177
 
171
- June 2017 BUNDLE-EXEC(1)
178
+ November 2018 BUNDLE-EXEC(1)
data/man/bundle-exec.ronn CHANGED
@@ -8,11 +8,11 @@ bundle-exec(1) -- Execute a command in the context of the bundle
8
8
  ## DESCRIPTION
9
9
 
10
10
  This command executes the command, making all gems specified in the
11
- `Gemfile(5)` available to `require` in Ruby programs.
11
+ [`Gemfile(5)`][Gemfile(5)] available to `require` in Ruby programs.
12
12
 
13
13
  Essentially, if you would normally have run something like
14
14
  `rspec spec/my_spec.rb`, and you want to use the gems specified
15
- in the `Gemfile(5)` and installed via [bundle install(1)][bundle-install], you
15
+ in the [`Gemfile(5)`][Gemfile(5)] and installed via [bundle install(1)](bundle-install.1.html), you
16
16
  should run `bundle exec rspec spec/my_spec.rb`.
17
17
 
18
18
  Note that `bundle exec` does not require that an executable is
@@ -27,7 +27,7 @@ available on your shell's `$PATH`.
27
27
 
28
28
  ## BUNDLE INSTALL --BINSTUBS
29
29
 
30
- If you use the `--binstubs` flag in [bundle install(1)][bundle-install], Bundler will
30
+ If you use the `--binstubs` flag in [bundle install(1)](bundle-install.1.html), Bundler will
31
31
  automatically create a directory (which defaults to `app_root/bin`)
32
32
  containing all of the executables available from gems in the bundle.
33
33
 
@@ -63,6 +63,13 @@ It also modifies Rubygems:
63
63
  making system executables work
64
64
  * Add all gems in the bundle into Gem.loaded_specs
65
65
 
66
+ Finally, `bundle exec` also implicitly modifies `Gemfile.lock` if the lockfile
67
+ and the Gemfile do not match. Bundler needs the Gemfile to determine things
68
+ such as a gem's groups, `autorequire`, and platforms, etc., and that
69
+ information isn't stored in the lockfile. The Gemfile and lockfile must be
70
+ synced in order to `bundle exec` successfully, so `bundle exec`
71
+ updates the lockfile beforehand.
72
+
66
73
  ### Loading
67
74
 
68
75
  By default, when attempting to `bundle exec` to a file with a ruby shebang,
data/man/bundle-gem.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\-GEM" "1" "July 2017" "" ""
4
+ .TH "BUNDLE\-GEM" "1" "November 2018" "" ""
5
5
  .
6
6
  .SH "NAME"
7
7
  \fBbundle\-gem\fR \- Generate a project skeleton for creating a rubygem
@@ -65,7 +65,7 @@ Do not create a \fBLICENSE\.txt\fR (overrides \fB\-\-mit\fR specified in the glo
65
65
  .
66
66
  .TP
67
67
  \fB\-t\fR, \fB\-\-test=minitest\fR, \fB\-\-test=rspec\fR
68
- Specify the test framework that Bundler should use when generating the project\. Acceptable values are \fBminitest\fR and \fBrspec\fR\. The \fBGEM_NAME\.gemspec\fR will be configured and a skeleton test/spec directory will be created based on this option\. If this option is unspecified, an interactive prompt will be displayed and the answer will be saved in Bundler\'s global config for future \fBbundle gem\fR use\.
68
+ Specify the test framework that Bundler should use when generating the project\. Acceptable values are \fBminitest\fR and \fBrspec\fR\. The \fBGEM_NAME\.gemspec\fR will be configured and a skeleton test/spec directory will be created based on this option\. If this option is unspecified, an interactive prompt will be displayed and the answer will be saved in Bundler\'s global config for future \fBbundle gem\fR use\. If no option is specified, the default testing framework is RSpec\.
69
69
  .
70
70
  .TP
71
71
  \fB\-e\fR, \fB\-\-edit[=EDITOR]\fR
@@ -74,7 +74,7 @@ Open the resulting GEM_NAME\.gemspec in EDITOR, or the default editor if not spe
74
74
  .SH "SEE ALSO"
75
75
  .
76
76
  .IP "\(bu" 4
77
- bundle\-config(1)
77
+ bundle config(1) \fIbundle\-config\.1\.html\fR
78
78
  .
79
79
  .IP "" 0
80
80
 
data/man/bundle-gem.1.txt CHANGED
@@ -2,89 +2,90 @@ BUNDLE-GEM(1) BUNDLE-GEM(1)
2
2
 
3
3
 
4
4
 
5
- 1mNAME0m
6
- 1mbundle-gem 22m- Generate a project skeleton for creating a rubygem
5
+ NAME
6
+ bundle-gem - Generate a project skeleton for creating a rubygem
7
7
 
8
- 1mSYNOPSIS0m
9
- 1mbundle gem 4m22mGEM_NAME24m 4mOPTIONS0m
8
+ SYNOPSIS
9
+ bundle gem GEM_NAME OPTIONS
10
10
 
11
- 1mDESCRIPTION0m
12
- Generates a directory named 1mGEM_NAME 22mwith a 1mRakefile22m, 1mGEM_NAME.gemspec22m,
11
+ DESCRIPTION
12
+ Generates a directory named GEM_NAME with a Rakefile, GEM_NAME.gemspec,
13
13
  and other supporting files and directories that can be used to develop
14
14
  a rubygem with that name.
15
15
 
16
- Run 1mrake -T 22min the resulting project for a list of Rake tasks that can
16
+ Run rake -T in the resulting project for a list of Rake tasks that can
17
17
  be used to test and publish the gem to rubygems.org.
18
18
 
19
19
  The generated project skeleton can be customized with OPTIONS, as
20
20
  explained below. Note that these options can also be specified via
21
21
  Bundler's global configuration file using the following names:
22
22
 
23
- o 1mgem.coc0m
23
+ o gem.coc
24
24
 
25
- o 1mgem.mit0m
25
+ o gem.mit
26
26
 
27
- o 1mgem.test0m
27
+ o gem.test
28
28
 
29
29
 
30
30
 
31
- 1mOPTIONS0m
32
- 1m--exe 22mor 1m-b 22mor 1m--bin0m
31
+ OPTIONS
32
+ --exe or -b or --bin
33
33
  Specify that Bundler should create a binary executable (as
34
- 1mexe/GEM_NAME22m) in the generated rubygem project. This binary will
35
- also be added to the 1mGEM_NAME.gemspec 22mmanifest. This behavior is
34
+ exe/GEM_NAME) in the generated rubygem project. This binary will
35
+ also be added to the GEM_NAME.gemspec manifest. This behavior is
36
36
  disabled by default.
37
37
 
38
- 1m--no-exe0m
39
- Do not create a binary (overrides 1m--exe 22mspecified in the global
38
+ --no-exe
39
+ Do not create a binary (overrides --exe specified in the global
40
40
  config).
41
41
 
42
- 1m--coc 22mAdd a 1mCODE_OF_CONDUCT.md 22mfile to the root of the generated
42
+ --coc Add a CODE_OF_CONDUCT.md file to the root of the generated
43
43
  project. If this option is unspecified, an interactive prompt
44
44
  will be displayed and the answer will be saved in Bundler's
45
- global config for future 1mbundle gem 22muse.
45
+ global config for future bundle gem use.
46
46
 
47
- 1m--no-coc0m
48
- Do not create a 1mCODE_OF_CONDUCT.md 22m(overrides 1m--coc 22mspecified in
47
+ --no-coc
48
+ Do not create a CODE_OF_CONDUCT.md (overrides --coc specified in
49
49
  the global config).
50
50
 
51
- 1m--ext 22mAdd boilerplate for C extension code to the generated project.
51
+ --ext Add boilerplate for C extension code to the generated project.
52
52
  This behavior is disabled by default.
53
53
 
54
- 1m--no-ext0m
55
- Do not add C extension code (overrides 1m--ext 22mspecified in the
54
+ --no-ext
55
+ Do not add C extension code (overrides --ext specified in the
56
56
  global config).
57
57
 
58
- 1m--mit 22mAdd an MIT license to a 1mLICENSE.txt 22mfile in the root of the gen-
58
+ --mit Add an MIT license to a LICENSE.txt file in the root of the gen-
59
59
  erated project. Your name from the global git config is used for
60
60
  the copyright statement. If this option is unspecified, an
61
61
  interactive prompt will be displayed and the answer will be
62
- saved in Bundler's global config for future 1mbundle gem 22muse.
62
+ saved in Bundler's global config for future bundle gem use.
63
63
 
64
- 1m--no-mit0m
65
- Do not create a 1mLICENSE.txt 22m(overrides 1m--mit 22mspecified in the
64
+ --no-mit
65
+ Do not create a LICENSE.txt (overrides --mit specified in the
66
66
  global config).
67
67
 
68
- 1m-t22m, 1m--test=minitest22m, 1m--test=rspec0m
68
+ -t, --test=minitest, --test=rspec
69
69
  Specify the test framework that Bundler should use when generat-
70
- ing the project. Acceptable values are 1mminitest 22mand 1mrspec22m. The
71
- 1mGEM_NAME.gemspec 22mwill be configured and a skeleton test/spec
70
+ ing the project. Acceptable values are minitest and rspec. The
71
+ GEM_NAME.gemspec will be configured and a skeleton test/spec
72
72
  directory will be created based on this option. If this option
73
73
  is unspecified, an interactive prompt will be displayed and the
74
- answer will be saved in Bundler's global config for future 1mbun-0m
75
- 1mdle gem 22muse.
74
+ answer will be saved in Bundler's global config for future bun-
75
+ dle gem use. If no option is specified, the default testing
76
+ framework is RSpec.
76
77
 
77
- 1m-e22m, 1m--edit[=EDITOR]0m
78
- Open the resulting GEM_NAME.gemspec in EDITOR, or the default
79
- editor if not specified. The default is 1m$BUNDLER_EDITOR22m, 1m$VIS-0m
80
- 1mUAL22m, or 1m$EDITOR22m.
78
+ -e, --edit[=EDITOR]
79
+ Open the resulting GEM_NAME.gemspec in EDITOR, or the default
80
+ editor if not specified. The default is $BUNDLER_EDITOR,
81
+ $VISUAL, or $EDITOR.
81
82
 
82
- 1mSEE ALSO0m
83
- o bundle-config(1)
83
+ SEE ALSO
84
+ o bundle config(1) bundle-config.1.html
84
85
 
85
86
 
86
87
 
87
88
 
88
89
 
89
90
 
90
- July 2017 BUNDLE-GEM(1)
91
+ November 2018 BUNDLE-GEM(1)
data/man/bundle-gem.ronn CHANGED
@@ -67,6 +67,7 @@ configuration file using the following names:
67
67
  on this option. If this option is unspecified, an interactive prompt will be
68
68
  displayed and the answer will be saved in Bundler's global config for future
69
69
  `bundle gem` use.
70
+ If no option is specified, the default testing framework is RSpec.
70
71
 
71
72
  * `-e`, `--edit[=EDITOR]`:
72
73
  Open the resulting GEM_NAME.gemspec in EDITOR, or the default editor if not
@@ -74,4 +75,4 @@ configuration file using the following names:
74
75
 
75
76
  ## SEE ALSO
76
77
 
77
- * bundle-config(1)
78
+ * [bundle config(1)](bundle-config.1.html)
data/man/bundle-info.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\-INFO" "1" "June 2017" "" ""
4
+ .TH "BUNDLE\-INFO" "1" "November 2018" "" ""
5
5
  .
6
6
  .SH "NAME"
7
7
  \fBbundle\-info\fR \- Show information for the given gem in your bundle
@@ -2,20 +2,20 @@ BUNDLE-INFO(1) BUNDLE-INFO(1)
2
2
 
3
3
 
4
4
 
5
- 1mNAME0m
6
- 1mbundle-info 22m- Show information for the given gem in your bundle
5
+ NAME
6
+ bundle-info - Show information for the given gem in your bundle
7
7
 
8
- 1mSYNOPSIS0m
9
- 1mbundle info 22m[GEM] [--path]
8
+ SYNOPSIS
9
+ bundle info [GEM] [--path]
10
10
 
11
- 1mDESCRIPTION0m
11
+ DESCRIPTION
12
12
  Print the basic information about the provided GEM such as homepage,
13
13
  version, path and summary.
14
14
 
15
- 1mOPTIONS0m
16
- 1m--path 22mPrint the path of the given gem
15
+ OPTIONS
16
+ --path Print the path of the given gem
17
17
 
18
18
 
19
19
 
20
20
 
21
- June 2017 BUNDLE-INFO(1)
21
+ November 2018 BUNDLE-INFO(1)
data/man/bundle-init.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\-INIT" "1" "June 2017" "" ""
4
+ .TH "BUNDLE\-INIT" "1" "November 2018" "" ""
5
5
  .
6
6
  .SH "NAME"
7
7
  \fBbundle\-init\fR \- Generates a Gemfile into the current working directory
@@ -10,11 +10,16 @@
10
10
  \fBbundle init\fR [\-\-gemspec=FILE]
11
11
  .
12
12
  .SH "DESCRIPTION"
13
- Init generates a default \fBGemfile(5)\fR in the current working directory\. When adding a \fBGemfile(5)\fR to a gem with a gemspec, the \fB\-\-gemspec\fR option will automatically add each dependency listed in the gemspec file to the newly created \fBGemfile(5)\fR\.
13
+ Init generates a default [\fBGemfile(5)\fR][Gemfile(5)] in the current working directory\. When adding a [\fBGemfile(5)\fR][Gemfile(5)] to a gem with a gemspec, the \fB\-\-gemspec\fR option will automatically add each dependency listed in the gemspec file to the newly created [\fBGemfile(5)\fR][Gemfile(5)]\.
14
14
  .
15
15
  .SH "OPTIONS"
16
16
  .
17
17
  .TP
18
18
  \fB\-\-gemspec\fR
19
- Use the specified \.gemspec to create the \fBGemfile(5)\fR
20
-
19
+ Use the specified \.gemspec to create the [\fBGemfile(5)\fR][Gemfile(5)]
20
+ .
21
+ .SH "FILES"
22
+ Included in the default [\fBGemfile(5)\fR][Gemfile(5)] generated is the line \fB# frozen_string_literal: true\fR\. This is a magic comment supported for the first time in Ruby 2\.3\. The presence of this line results in all string literals in the file being implicitly frozen\.
23
+ .
24
+ .SH "SEE ALSO"
25
+ Gemfile(5) \fIhttp://bundler\.io/man/gemfile\.5\.html\fR
@@ -2,23 +2,33 @@ BUNDLE-INIT(1) BUNDLE-INIT(1)
2
2
 
3
3
 
4
4
 
5
- 1mNAME0m
6
- 1mbundle-init 22m- Generates a Gemfile into the current working directory
5
+ NAME
6
+ bundle-init - Generates a Gemfile into the current working directory
7
7
 
8
- 1mSYNOPSIS0m
9
- 1mbundle init 22m[--gemspec=FILE]
8
+ SYNOPSIS
9
+ bundle init [--gemspec=FILE]
10
10
 
11
- 1mDESCRIPTION0m
12
- Init generates a default 1mGemfile(5) 22min the current working directory.
13
- When adding a 1mGemfile(5) 22mto a gem with a gemspec, the 1m--gemspec 22moption
14
- will automatically add each dependency listed in the gemspec file to
15
- the newly created 1mGemfile(5)22m.
11
+ DESCRIPTION
12
+ Init generates a default [Gemfile(5)][Gemfile(5)] in the current work-
13
+ ing directory. When adding a [Gemfile(5)][Gemfile(5)] to a gem with a
14
+ gemspec, the --gemspec option will automatically add each dependency
15
+ listed in the gemspec file to the newly created [Gemfile(5)][Gem-
16
+ file(5)].
16
17
 
17
- 1mOPTIONS0m
18
- 1m--gemspec0m
19
- Use the specified .gemspec to create the 1mGemfile(5)0m
18
+ OPTIONS
19
+ --gemspec
20
+ Use the specified .gemspec to create the [Gemfile(5)][Gem-
21
+ file(5)]
20
22
 
23
+ FILES
24
+ Included in the default [Gemfile(5)][Gemfile(5)] generated is the line
25
+ # frozen_string_literal: true. This is a magic comment supported for
26
+ the first time in Ruby 2.3. The presence of this line results in all
27
+ string literals in the file being implicitly frozen.
21
28
 
29
+ SEE ALSO
30
+ Gemfile(5) http://bundler.io/man/gemfile.5.html
22
31
 
23
32
 
24
- June 2017 BUNDLE-INIT(1)
33
+
34
+ November 2018 BUNDLE-INIT(1)
data/man/bundle-init.ronn CHANGED
@@ -7,12 +7,23 @@ bundle-init(1) -- Generates a Gemfile into the current working directory
7
7
 
8
8
  ## DESCRIPTION
9
9
 
10
- Init generates a default `Gemfile(5)` in the current working directory. When
11
- adding a `Gemfile(5)` to a gem with a gemspec, the `--gemspec` option will
10
+ Init generates a default [`Gemfile(5)`][Gemfile(5)] in the current working directory. When
11
+ adding a [`Gemfile(5)`][Gemfile(5)] to a gem with a gemspec, the `--gemspec` option will
12
12
  automatically add each dependency listed in the gemspec file to the newly
13
- created `Gemfile(5)`.
13
+ created [`Gemfile(5)`][Gemfile(5)].
14
14
 
15
15
  ## OPTIONS
16
16
 
17
17
  * `--gemspec`:
18
- Use the specified .gemspec to create the `Gemfile(5)`
18
+ Use the specified .gemspec to create the [`Gemfile(5)`][Gemfile(5)]
19
+
20
+ ## FILES
21
+
22
+ Included in the default [`Gemfile(5)`][Gemfile(5)]
23
+ generated is the line `# frozen_string_literal: true`. This is a magic comment
24
+ supported for the first time in Ruby 2.3. The presence of this line
25
+ results in all string literals in the file being implicitly frozen.
26
+
27
+ ## SEE ALSO
28
+
29
+ [Gemfile(5)](http://bundler.io/man/gemfile.5.html)
data/man/bundle-inject.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\-INJECT" "1" "June 2017" "" ""
4
+ .TH "BUNDLE\-INJECT" "1" "November 2018" "" ""
5
5
  .
6
6
  .SH "NAME"
7
7
  \fBbundle\-inject\fR \- Add named gem(s) with version requirements to Gemfile
@@ -10,10 +10,10 @@
10
10
  \fBbundle inject\fR [GEM] [VERSION]
11
11
  .
12
12
  .SH "DESCRIPTION"
13
- Adds the named gem(s) with their version requirements to the resolved \fBGemfile(5)\fR\.
13
+ Adds the named gem(s) with their version requirements to the resolved [\fBGemfile(5)\fR][Gemfile(5)]\.
14
14
  .
15
15
  .P
16
- This command will add the gem to both your \fBGemfile(5)\fR and Gemfile\.lock if it isn\'t listed yet\.
16
+ This command will add the gem to both your [\fBGemfile(5)\fR][Gemfile(5)] and Gemfile\.lock if it isn\'t listed yet\.
17
17
  .
18
18
  .P
19
19
  Example:
@@ -30,4 +30,4 @@ bundle inject \'rack\' \'> 0\'
30
30
  .IP "" 0
31
31
  .
32
32
  .P
33
- This will inject the \'rack\' gem with a version greater than 0 in your \fBGemfile(5)\fR and Gemfile\.lock
33
+ This will inject the \'rack\' gem with a version greater than 0 in your [\fBGemfile(5)\fR][Gemfile(5)] and Gemfile\.lock