ruby-changes:57783
From: Hiroshi <ko1@a...>
Date: Wed, 18 Sep 2019 19:21:41 +0900 (JST)
Subject: [ruby-changes:57783] ba86353446 (master): Update the latest documentation of bundler
https://git.ruby-lang.org/ruby.git/commit/?id=ba86353446 From ba86353446f6c1ce9b2c95d03bf16cfed3a532d2 Mon Sep 17 00:00:00 2001 From: Hiroshi SHIBATA <hsbt@r...> Date: Wed, 18 Sep 2019 15:28:08 +0900 Subject: Update the latest documentation of bundler diff --git a/man/bundle-add.1 b/man/bundle-add.1 index 892a09f..1136123 100644 --- a/man/bundle-add.1 +++ b/man/bundle-add.1 @@ -1,7 +1,7 @@ https://github.com/ruby/ruby/blob/trunk/man/bundle-add.1#L1 .\" generated with Ronn/v0.7.3 .\" http://github.com/rtomayko/ronn/tree/0.7.3 . -.TH "BUNDLE\-ADD" "1" "August 2019" "" "" +.TH "BUNDLE\-ADD" "1" "September 2019" "" "" . .SH "NAME" \fBbundle\-add\fR \- Add gem to the Gemfile and run bundle install diff --git a/man/bundle-add.1.txt b/man/bundle-add.1.txt index 1d3723c..8379dbc 100644 --- a/man/bundle-add.1.txt +++ b/man/bundle-add.1.txt @@ -55,4 +55,4 @@ OPTIONS https://github.com/ruby/ruby/blob/trunk/man/bundle-add.1.txt#L55 - August 2019 BUNDLE-ADD(1) + September 2019 BUNDLE-ADD(1) diff --git a/man/bundle-binstubs.1 b/man/bundle-binstubs.1 index 7fe74d0..bcfe600 100644 --- a/man/bundle-binstubs.1 +++ b/man/bundle-binstubs.1 @@ -1,7 +1,7 @@ https://github.com/ruby/ruby/blob/trunk/man/bundle-binstubs.1#L1 .\" generated with Ronn/v0.7.3 .\" http://github.com/rtomayko/ronn/tree/0.7.3 . -.TH "BUNDLE\-BINSTUBS" "1" "August 2019" "" "" +.TH "BUNDLE\-BINSTUBS" "1" "September 2019" "" "" . .SH "NAME" \fBbundle\-binstubs\fR \- Install the binstubs of the listed gems diff --git a/man/bundle-binstubs.1.txt b/man/bundle-binstubs.1.txt index 6dd50a5..7a45ecc 100644 --- a/man/bundle-binstubs.1.txt +++ b/man/bundle-binstubs.1.txt @@ -45,4 +45,4 @@ BUNDLE INSTALL --BINSTUBS https://github.com/ruby/ruby/blob/trunk/man/bundle-binstubs.1.txt#L45 - August 2019 BUNDLE-BINSTUBS(1) + September 2019 BUNDLE-BINSTUBS(1) diff --git a/man/bundle-check.1 b/man/bundle-check.1 index 12ee707..90df9ca 100644 --- a/man/bundle-check.1 +++ b/man/bundle-check.1 @@ -1,7 +1,7 @@ https://github.com/ruby/ruby/blob/trunk/man/bundle-check.1#L1 .\" generated with Ronn/v0.7.3 .\" http://github.com/rtomayko/ronn/tree/0.7.3 . -.TH "BUNDLE\-CHECK" "1" "August 2019" "" "" +.TH "BUNDLE\-CHECK" "1" "September 2019" "" "" . .SH "NAME" \fBbundle\-check\fR \- Verifies if dependencies are satisfied by installed gems diff --git a/man/bundle-check.1.txt b/man/bundle-check.1.txt index 08ef075..7e24698 100644 --- a/man/bundle-check.1.txt +++ b/man/bundle-check.1.txt @@ -9,8 +9,8 @@ SYNOPSIS https://github.com/ruby/ruby/blob/trunk/man/bundle-check.1.txt#L9 bundle check [--dry-run] [--gemfile=FILE] [--path=PATH] DESCRIPTION - check searches the local machine for each of the gems requested in the - Gemfile. If all gems are found, Bundler prints a success message and + check searches the local machine for each of the gems requested in the + Gemfile. If all gems are found, Bundler prints a success message and exits with a status of 0. If not, the first missing gem is listed and Bundler exits status 1. @@ -20,14 +20,14 @@ OPTIONS https://github.com/ruby/ruby/blob/trunk/man/bundle-check.1.txt#L20 Locks the [Gemfile(5)][Gemfile(5)] before running the command. --gemfile - Use the specified gemfile instead of the [Gemfile(5)][Gem- + Use the specified gemfile instead of the [Gemfile(5)][Gem- file(5)]. - --path Specify a different path than the system default ($BUNDLE_PATH - or $GEM_HOME). Bundler will remember this value for future + --path Specify a different path than the system default ($BUNDLE_PATH + or $GEM_HOME). Bundler will remember this value for future installs on this machine. - August 2019 BUNDLE-CHECK(1) + September 2019 BUNDLE-CHECK(1) diff --git a/man/bundle-clean.1 b/man/bundle-clean.1 index d7813e2..76dcee2 100644 --- a/man/bundle-clean.1 +++ b/man/bundle-clean.1 @@ -1,7 +1,7 @@ https://github.com/ruby/ruby/blob/trunk/man/bundle-clean.1#L1 .\" generated with Ronn/v0.7.3 .\" http://github.com/rtomayko/ronn/tree/0.7.3 . -.TH "BUNDLE\-CLEAN" "1" "August 2019" "" "" +.TH "BUNDLE\-CLEAN" "1" "September 2019" "" "" . .SH "NAME" \fBbundle\-clean\fR \- Cleans up unused gems in your bundler directory diff --git a/man/bundle-clean.1.txt b/man/bundle-clean.1.txt index 5f94128..f3d9c77 100644 --- a/man/bundle-clean.1.txt +++ b/man/bundle-clean.1.txt @@ -23,4 +23,4 @@ OPTIONS https://github.com/ruby/ruby/blob/trunk/man/bundle-clean.1.txt#L23 - August 2019 BUNDLE-CLEAN(1) + September 2019 BUNDLE-CLEAN(1) diff --git a/man/bundle-config.1 b/man/bundle-config.1 index eda7379..ce670f7 100644 --- a/man/bundle-config.1 +++ b/man/bundle-config.1 @@ -1,7 +1,7 @@ https://github.com/ruby/ruby/blob/trunk/man/bundle-config.1#L1 .\" generated with Ronn/v0.7.3 .\" http://github.com/rtomayko/ronn/tree/0.7.3 . -.TH "BUNDLE\-CONFIG" "1" "August 2019" "" "" +.TH "BUNDLE\-CONFIG" "1" "September 2019" "" "" . .SH "NAME" \fBbundle\-config\fR \- Set bundler configuration options diff --git a/man/bundle-config.1.txt b/man/bundle-config.1.txt index e4570be..7c601a8 100644 --- a/man/bundle-config.1.txt +++ b/man/bundle-config.1.txt @@ -65,29 +65,29 @@ REMEMBERING OPTIONS https://github.com/ruby/ruby/blob/trunk/man/bundle-config.1.txt#L65 foo or --without production, are remembered between commands and saved to your local application's configuration (normally, ./.bundle/config). - However, this will be changed in bundler 3, so it's better not to rely - on this behavior. If these options must be remembered, it's better to + However, this will be changed in bundler 3, so it's better not to rely + on this behavior. If these options must be remembered, it's better to set them using bundle config (e.g., bundle config set path foo). The options that can be configured are: - bin Creates a directory (defaults to ~/bin) and place any executa- + bin Creates a directory (defaults to ~/bin) and place any executa- bles from the gem there. These executables run in Bundler's con- - text. If used, you might add this directory to your environ- - ment's PATH variable. For instance, if the rails gem comes with + text. If used, you might add this directory to your environ- + ment's PATH variable. For instance, if the rails gem comes with a rails executable, this flag will create a bin/rails executable - that ensures that all referred dependencies will be resolved + that ensures that all referred dependencies will be resolved using the bundled gems. deployment - In deployment mode, Bundler will 'roll-out' the bundle for pro- - duction use. Please check carefully if you want to have this + In deployment mode, Bundler will 'roll-out' the bundle for pro- + duction use. Please check carefully if you want to have this option enabled in development or test environments. - path The location to install the specified gems to. This defaults to - Rubygems' setting. Bundler shares this location with Rubygems, - gem install ... will have gem installed there, too. Therefore, - gems installed without a --path ... setting will show up by + path The location to install the specified gems to. This defaults to + Rubygems' setting. Bundler shares this location with Rubygems, + gem install ... will have gem installed there, too. Therefore, + gems installed without a --path ... setting will show up by calling gem list. Accordingly, gems installed to other locations will not get listed. @@ -95,15 +95,15 @@ REMEMBERING OPTIONS https://github.com/ruby/ruby/blob/trunk/man/bundle-config.1.txt#L95 A space-separated list of groups referencing gems to skip during installation. - with A space-separated list of groups referencing gems to include + with A space-separated list of groups referencing gems to include during installation. BUILD OPTIONS - You can use bundle config to give Bundler the flags to pass to the gem + You can use bundle config to give Bundler the flags to pass to the gem installer every time bundler tries to install a particular gem. - A very common example, the mysql gem, requires Snow Leopard users to - pass configuration flags to gem install to specify where to find the + A very common example, the mysql gem, requires Snow Leopard users to + pass configuration flags to gem install to specify where to find the mysql_config executable. @@ -112,7 +112,7 @@ BUILD OPTIONS https://github.com/ruby/ruby/blob/trunk/man/bundle-config.1.txt#L112 - Since the specific location of that executable can change from machine + Since the specific location of that executable can change from machine to machine, you can specify these flags on a per-machine basis. @@ -121,43 +121,43 @@ BUILD OPTIONS https://github.com/ruby/ruby/blob/trunk/man/bundle-config.1.txt#L121 - After running this command, every time bundler needs to install the + After running this command, every time bundler needs to install the mysql gem, it will pass along the flags you specified. CONFIGURATION KEYS - Configuration keys in bundler have two forms: the canonical form and + Configuration keys in bundler have two forms: the canonical form and the environment variable form. - For instance, passing the --without flag to bundle install(1) bun- - dle-install.1.html prevents Bundler from installing certain groups - specified in the Gemfile(5). Bundler persists this value in app/.bun- - dle/config so that (... truncated) -- ML: ruby-changes@q... Info: http://www.atdot.net/~ko1/quickml/