rubygems-update 3.1.2 → 3.2.3

data/bundler/man/bundle-list.1.txt

@@ -1,43 +0,0 @@
-BUNDLE-LIST(1)							BUNDLE-LIST(1)
-
-
-
-NAME
-       bundle-list - List all the gems in the bundle
-
-SYNOPSIS
-       bundle	 list	 [--name-only]	  [--paths]    [--without-group=GROUP]
-       [--only-group=GROUP]
-
-DESCRIPTION
-       Prints a list of all the gems in the bundle including their version.
-
-       Example:
-
-       bundle list --name-only
-
-       bundle list --paths
-
-       bundle list --without-group test
-
-       bundle list --only-group dev
-
-       bundle list --only-group dev --paths
-
-OPTIONS
-       --name-only
-	      Print only the name of each gem.
-
-       --paths
-	      Print the path to each gem in the bundle.
-
-       --without-group
-	      Print all gems expect from a group.
-
-       --only-group
-	      Print gems from a particular group.
-
-
-
-
-				 December 2019			BUNDLE-LIST(1)

data/bundler/man/bundle-lock.1.txt

@@ -1,93 +0,0 @@
-BUNDLE-LOCK(1)							BUNDLE-LOCK(1)
-
-
-
-NAME
-       bundle-lock - Creates / Updates a lockfile without installing
-
-SYNOPSIS
-       bundle	 lock	[--update]   [--local]	 [--print]   [--lockfile=PATH]
-       [--full-index] [--add-platform] [--remove-platform] [--patch] [--minor]
-       [--major] [--strict] [--conservative]
-
-DESCRIPTION
-       Lock the gems specified in Gemfile.
-
-OPTIONS
-       --update=<*gems>
-	      Ignores  the  existing  lockfile. Resolve then updates lockfile.
-	      Taking a list of gems or updating all gems if no list is given.
-
-       --local
-	      Do not attempt to connect to rubygems.org. Instead, Bundler will
-	      use  the	gems  already  present	in  Rubygems' cache or in ven-
-	      dor/cache. Note that  if	a  appropriate	platform-specific  gem
-	      exists on rubygems.org it will not be found.
-
-       --print
-	      Prints  the  lockfile  to  STDOUT instead of writing to the file
-	      system.
-
-       --lockfile=<path>
-	      The path where the lockfile should be written to.
-
-       --full-index
-	      Fall back to using the single-file index of all gems.
-
-       --add-platform
-	      Add a new platform to the lockfile, re-resolving for  the  addi-
-	      tion of that platform.
-
-       --remove-platform
-	      Remove a platform from the lockfile.
-
-       --patch
-	      If updating, prefer updating only to next patch version.
-
-       --minor
-	      If updating, prefer updating only to next minor version.
-
-       --major
-	      If updating, prefer updating to next major version (default).
-
-       --strict
-	      If  updating,  do  not  allow  any gem to be updated past latest
-	      --patch | --minor | --major.
-
-       --conservative
-	      If updating, use bundle install conservative update behavior and
-	      do not allow shared dependencies to be updated.
-
-UPDATING ALL GEMS
-       If  you	run  bundle  lock  with  --update option without list of gems,
-       bundler will ignore any	previously  installed  gems  and  resolve  all
-       dependencies  again  based on the latest versions of all gems available
-       in the sources.
-
-UPDATING A LIST OF GEMS
-       Sometimes, you want to update a single gem in the Gemfile(5), and leave
-       the  rest  of the gems that you specified locked to the versions in the
-       Gemfile.lock.
-
-       For instance, you  only	want  to  update  nokogiri,  run  bundle  lock
-       --update nokogiri.
-
-       Bundler will update nokogiri and any of its dependencies, but leave the
-       rest of the gems that you specified locked to the versions in the  Gem-
-       file.lock.
-
-SUPPORTING OTHER PLATFORMS
-       If  you want your bundle to support platforms other than the one you're
-       running locally, you can run bundle lock --add-platform PLATFORM to add
-       PLATFORM  to the lockfile, force bundler to re-resolve and consider the
-       new platform when picking gems, all without needing to have  a  machine
-       that matches PLATFORM handy to install those platform-specific gems on.
-
-       For a full explanation of gem platforms, see gem help platform.
-
-PATCH LEVEL OPTIONS
-       See bundle update(1) bundle-update.1.html for details.
-
-
-
-				 December 2019			BUNDLE-LOCK(1)

data/bundler/man/bundle-open.1.txt

@@ -1,29 +0,0 @@
-BUNDLE-OPEN(1)							BUNDLE-OPEN(1)
-
-
-
-NAME
-       bundle-open - Opens the source directory for a gem in your bundle
-
-SYNOPSIS
-       bundle open [GEM]
-
-DESCRIPTION
-       Opens the source directory of the provided GEM in your editor.
-
-       For  this to work the EDITOR or BUNDLER_EDITOR environment variable has
-       to be set.
-
-       Example:
-
-
-
-	   bundle open 'rack'
-
-
-
-       Will open the source directory for the 'rack' gem in your bundle.
-
-
-
-				 December 2019			BUNDLE-OPEN(1)

data/bundler/man/bundle-outdated.1.txt

@@ -1,131 +0,0 @@
-BUNDLE-OUTDATED(1)					    BUNDLE-OUTDATED(1)
-
-
-
-NAME
-       bundle-outdated - List installed gems with newer versions available
-
-SYNOPSIS
-       bundle	outdated   [GEM]   [--local]   [--pre]	[--source]  [--strict]
-       [--parseable	|     --porcelain]     [--group=GROUP]	    [--groups]
-       [--update-strict]  [--patch|--minor|--major]  [--filter-major]  [--fil-
-       ter-minor] [--filter-patch] [--only-explicit]
-
-DESCRIPTION
-       Outdated lists the names and versions of gems that have a newer version
-       available  in  the given source. Calling outdated with [GEM [GEM]] will
-       only check for newer versions of the given gems.  Prerelease  gems  are
-       ignored by default. If your gems are up to date, Bundler will exit with
-       a status of 0. Otherwise, it will exit 1.
-
-OPTIONS
-       --local
-	      Do not attempt to fetch gems remotely  and  use  the  gem  cache
-	      instead.
-
-       --pre  Check for newer pre-release gems.
-
-       --source
-	      Check against a specific source.
-
-       --strict
-	      Only list newer versions allowed by your Gemfile requirements.
-
-       --parseable, --porcelain
-	      Use minimal formatting for more parseable output.
-
-       --group
-	      List gems from a specific group.
-
-       --groups
-	      List gems organized by groups.
-
-       --update-strict
-	      Strict  conservative  resolution,  do  not  allow  any gem to be
-	      updated past latest --patch | --minor| --major.
-
-       --minor
-	      Prefer updating only to next minor version.
-
-       --major
-	      Prefer updating to next major version (default).
-
-       --patch
-	      Prefer updating only to next patch version.
-
-       --filter-major
-	      Only list major newer versions.
-
-       --filter-minor
-	      Only list minor newer versions.
-
-       --filter-patch
-	      Only list patch newer versions.
-
-       --only-explicit
-	      Only list gems specified in your Gemfile,  not  their  dependen-
-	      cies.
-
-PATCH LEVEL OPTIONS
-       See bundle update(1) bundle-update.1.html for details.
-
-       One  difference	between  the  patch level options in bundle update and
-       here is the --strict option. --strict was already an option on outdated
-       before the patch level options were added. --strict wasn't altered, and
-       the --update-strict option on outdated reflects what --strict  does  on
-       bundle update.
-
-FILTERING OUTPUT
-       The  3  filtering  options  do  not  affect the resolution of versions,
-       merely what versions are shown in the output.
-
-       If the regular output shows the following:
-
-
-
-	   * faker (newest 1.6.6, installed 1.6.5, requested ~> 1.4) in groups "development, test"
-	   * hashie (newest 3.4.6, installed 1.2.0, requested = 1.2.0) in groups "default"
-	   * headless (newest 2.3.1, installed 2.2.3) in groups "test"
-
-
-
-       --filter-major would only show:
-
-
-
-	   * hashie (newest 3.4.6, installed 1.2.0, requested = 1.2.0) in groups "default"
-
-
-
-       --filter-minor would only show:
-
-
-
-	   * headless (newest 2.3.1, installed 2.2.3) in groups "test"
-
-
-
-       --filter-patch would only show:
-
-
-
-	   * faker (newest 1.6.6, installed 1.6.5, requested ~> 1.4) in groups "development, test"
-
-
-
-       Filter options can be combined. --filter-minor and --filter-patch would
-       show:
-
-
-
-	   * faker (newest 1.6.6, installed 1.6.5, requested ~> 1.4) in groups "development, test"
-	   * headless (newest 2.3.1, installed 2.2.3) in groups "test"
-
-
-
-       Combining  all three filter options would be the same result as provid-
-       ing none of them.
-
-
-
-				 December 2019		    BUNDLE-OUTDATED(1)

data/bundler/man/bundle-platform.1.txt

@@ -1,57 +0,0 @@
-BUNDLE-PLATFORM(1)					    BUNDLE-PLATFORM(1)
-
-
-
-NAME
-       bundle-platform - Displays platform compatibility information
-
-SYNOPSIS
-       bundle platform [--ruby]
-
-DESCRIPTION
-       platform  will display information from your Gemfile, Gemfile.lock, and
-       Ruby VM about your platform.
-
-       For instance, using this Gemfile(5):
-
-
-
-	   source "https://rubygems.org"
-
-	   ruby "1.9.3"
-
-	   gem "rack"
-
-
-
-       If you run bundle platform on Ruby 1.9.3, it will display the following
-       output:
-
-
-
-	   Your platform is: x86_64-linux
-
-	   Your app has gems that work on these platforms:
-	   * ruby
-
-	   Your Gemfile specifies a Ruby version requirement:
-	   * ruby 1.9.3
-
-	   Your current platform satisfies the Ruby version requirement.
-
-
-
-       platform  will  list  all the platforms in your Gemfile.lock as well as
-       the ruby directive if applicable from your Gemfile(5). It will also let
-       you know if the ruby directive requirement has been met. If ruby direc-
-       tive doesn't match the running Ruby VM, it will tell you what part does
-       not.
-
-OPTIONS
-       --ruby It  will	display  the  ruby directive information, so you don't
-	      have to parse it from the Gemfile(5).
-
-
-
-
-				 December 2019		    BUNDLE-PLATFORM(1)

data/bundler/man/bundle-pristine.1.txt

@@ -1,44 +0,0 @@
-BUNDLE-PRISTINE(1)					    BUNDLE-PRISTINE(1)
-
-
-
-NAME
-       bundle-pristine - Restores installed gems to their pristine condition
-
-SYNOPSIS
-       bundle pristine
-
-DESCRIPTION
-       pristine  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.
-
-       For  further  explanation,  bundle  pristine  ignores unpacked files on
-       disk. In other words, this command utilizes the local .gem cache or the
-       gem's git repository as if one were installing from scratch.
-
-       Note:  the  Bundler  gem  cannot be restored to its original state with
-       pristine. One also cannot use bundle pristine on  gems  with  a	'path'
-       option  in  the	Gemfile,  because  bundler has no original copy it can
-       restore from.
-
-       When is it practical to use bundle pristine?
-
-       It comes in handy when a developer is debugging a gem. bundle  pristine
-       is a great way to get rid of experimental changes to a gem that one may
-       not want.
-
-       Why use bundle pristine over gem pristine --all?
-
-       Both commands are very similar. For context: bundle  pristine,  without
-       arguments,  cleans  all gems from the lockfile. Meanwhile, gem pristine
-       --all cleans all installed gems for that Ruby version.
-
-       If a developer forgets which gems in their project they might have been
-       debugging,  the Rubygems gem pristine [GEMNAME] command may be inconve-
-       nient. One can avoid waiting for gem pristine --all,  and  instead  run
-       bundle pristine.
-
-
-
-				 December 2019		    BUNDLE-PRISTINE(1)

data/bundler/man/bundle-remove.1.txt

@@ -1,34 +0,0 @@
-BUNDLE-REMOVE(1)					      BUNDLE-REMOVE(1)
-
-
-
-NAME
-       bundle-remove - Removes gems from the Gemfile
-
-SYNOPSIS
-       bundle remove [GEM [GEM ...]] [--install]
-
-DESCRIPTION
-       Removes the given gems from the Gemfile while ensuring that the result-
-       ing 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.
-
-OPTIONS
-       --install
-	      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).
-
-       Example:
-
-       bundle remove rails
-
-       bundle remove rails rack
-
-       bundle remove rails rack --install
-
-
-
-				 December 2019		      BUNDLE-REMOVE(1)

data/bundler/man/bundle-show.1.txt

@@ -1,27 +0,0 @@
-BUNDLE-SHOW(1)							BUNDLE-SHOW(1)
-
-
-
-NAME
-       bundle-show - Shows all the gems in your bundle, or the path to a gem
-
-SYNOPSIS
-       bundle show [GEM] [--paths]
-
-DESCRIPTION
-       Without	the [GEM] option, show will print a list of the names and ver-
-       sions of all gems that are required by  your  [Gemfile(5)][Gemfile(5)],
-       sorted by name.
-
-       Calling	show  with  [GEM]  will list the exact location of that gem on
-       your machine.
-
-OPTIONS
-       --paths
-	      List the paths of all gems  that	are  required  by  your  [Gem-
-	      file(5)][Gemfile(5)], sorted by gem name.
-
-
-
-
-				 December 2019			BUNDLE-SHOW(1)