bundler 2.1.4 → 2.3.12

data/man/bundle-exec.1.txt

@@ -1,178 +0,0 @@
-BUNDLE-EXEC(1)							BUNDLE-EXEC(1)
-
-
-
-NAME
-       bundle-exec - Execute a command in the context of the bundle
-
-SYNOPSIS
-       bundle exec [--keep-file-descriptors] command
-
-DESCRIPTION
-       This  command  executes	the  command, making all gems specified in the
-       [Gemfile(5)][Gemfile(5)] available to require in Ruby programs.
-
-       Essentially, if you  would  normally  have  run	something  like  rspec
-       spec/my_spec.rb,  and  you  want to use the gems specified in the [Gem-
-       file(5)][Gemfile(5)]  and  installed   via   bundle   install(1)   bun-
-       dle-install.1.html, you should run bundle exec rspec spec/my_spec.rb.
-
-       Note  that bundle exec does not require that an executable is available
-       on your shell's $PATH.
-
-OPTIONS
-       --keep-file-descriptors
-	      Exec in Ruby 2.0 began discarding non-standard file descriptors.
-	      When  this flag is passed, exec will revert to the 1.9 behaviour
-	      of passing all file descriptors to the new process.
-
-BUNDLE INSTALL --BINSTUBS
-       If  you	use  the   --binstubs	flag   in   bundle   install(1)   bun-
-       dle-install.1.html,  Bundler  will  automatically  create  a  directory
-       (which defaults to app_root/bin)  containing  all  of  the  executables
-       available from gems in the bundle.
-
-       After  using --binstubs, bin/rspec spec/my_spec.rb is identical to bun-
-       dle exec rspec spec/my_spec.rb.
-
-ENVIRONMENT MODIFICATIONS
-       bundle exec makes a number of changes to the  shell  environment,  then
-       executes the command you specify in full.
-
-       o   make  sure  that  it's  still  possible to shell out to bundle from
-	   inside a command invoked by bundle exec (using $BUNDLE_BIN_PATH)
-
-       o   put	the  directory	containing  executables  (like	rails,	rspec,
-	   rackup) for your bundle on $PATH
-
-       o   make  sure  that if bundler is invoked in the subshell, it uses the
-	   same Gemfile (by setting BUNDLE_GEMFILE)
-
-       o   add -rbundler/setup to $RUBYOPT, which makes sure  that  Ruby  pro-
-	   grams invoked in the subshell can see the gems in the bundle
-
-
-
-       It also modifies Rubygems:
-
-       o   disallow loading additional gems not in the bundle
-
-       o   modify  the gem method to be a no-op if a gem matching the require-
-	   ments is in the bundle, and to raise a Gem::LoadError if it's not
-
-       o   Define Gem.refresh to be a no-op, since the source index is	always
-	   frozen  when  using	bundler,  and  to prevent gems from the system
-	   leaking into the environment
-
-       o   Override Gem.bin_path to use the gems in the bundle, making	system
-	   executables work
-
-       o   Add all gems in the bundle into Gem.loaded_specs
-
-
-
-       Finally, bundle exec also implicitly modifies Gemfile.lock if the lock-
-       file and the Gemfile do not match. Bundler needs the Gemfile to	deter-
-       mine  things  such as a gem's groups, autorequire, and platforms, etc.,
-       and that information isn't stored in  the  lockfile.  The  Gemfile  and
-       lockfile must be synced in order to bundle exec successfully, so bundle
-       exec updates the lockfile beforehand.
-
-   Loading
-       By default, when attempting to bundle exec to a file with a  ruby  she-
-       bang,  Bundler will Kernel.load that file instead of using Kernel.exec.
-       For the vast majority of cases, this is a performance improvement. In a
-       rare  few  cases,  this	could  cause some subtle side-effects (such as
-       dependence on the exact contents of $0 or __FILE__) and	the  optimiza-
-       tion can be disabled by enabling the disable_exec_load setting.
-
-   Shelling out
-       Any  Ruby  code that opens a subshell (like system, backticks, or %x{})
-       will automatically use the current Bundler environment. If you need  to
-       shell  out  to  a Ruby command that is not part of your current bundle,
-       use the with_clean_env method  with  a  block.  Any  subshells  created
-       inside  the  block will be given the environment present before Bundler
-       was activated. For example, Homebrew commands run Ruby, but don't  work
-       inside a bundle:
-
-
-
-	   Bundler.with_clean_env do
-	     `brew install wget`
-	   end
-
-
-
-       Using  with_clean_env  is  also	necessary if you are shelling out to a
-       different bundle. Any Bundler commands run in a subshell  will  inherit
-       the  current  Gemfile, so commands that need to run in the context of a
-       different bundle also need to use with_clean_env.
-
-
-
-	   Bundler.with_clean_env do
-	     Dir.chdir "/other/bundler/project" do
-	       `bundle exec ./script`
-	     end
-	   end
-
-
-
-       Bundler provides convenience helpers that wrap  system  and  exec,  and
-       they can be used like this:
-
-
-
-	   Bundler.clean_system('brew install wget')
-	   Bundler.clean_exec('brew install wget')
-
-
-
-RUBYGEMS PLUGINS
-       At  present,  the  Rubygems  plugin  system  requires  all  files named
-       rubygems_plugin.rb on the load path of any installed gem when any  Ruby
-       code requires rubygems.rb. This includes executables installed into the
-       system, like rails, rackup, and rspec.
-
-       Since Rubygems plugins can contain arbitrary Ruby code,	they  commonly
-       end up activating themselves or their dependencies.
-
-       For  instance,  the gemcutter 0.5 gem depended on json_pure. If you had
-       that version of gemcutter installed (even if you also had a newer  ver-
-       sion  without  this problem), Rubygems would activate gemcutter 0.5 and
-       json_pure <latest>.
-
-       If your Gemfile(5) also contained json_pure (or a gem with a dependency
-       on  json_pure),	the  latest version on your system might conflict with
-       the version in your Gemfile(5), or the snapshot version	in  your  Gem-
-       file.lock.
-
-       If this happens, bundler will say:
-
-
-
-	   You have already activated json_pure 1.4.6 but your Gemfile
-	   requires json_pure 1.4.3. Consider using bundle exec.
-
-
-
-       In  this  situation, you almost certainly want to remove the underlying
-       gem with the problematic gem plugin. In general, the authors  of  these
-       plugins	(in this case, the gemcutter gem) have released newer versions
-       that are more careful in their plugins.
-
-       You can find a list of all the gems containing gem plugins by running
-
-
-
-	   ruby -rrubygems -e "puts Gem.find_files('rubygems_plugin.rb')"
-
-
-
-       At the very least, you should remove all but the newest version of each
-       gem  plugin, and also remove all gem plugins that you aren't using (gem
-       uninstall gem_name).
-
-
-
-				 January 2020			BUNDLE-EXEC(1)

data/man/bundle-gem.1.txt

@@ -1,91 +0,0 @@
-BUNDLE-GEM(1)							 BUNDLE-GEM(1)
-
-
-
-NAME
-       bundle-gem - Generate a project skeleton for creating a rubygem
-
-SYNOPSIS
-       bundle gem GEM_NAME OPTIONS
-
-DESCRIPTION
-       Generates a directory named GEM_NAME with a Rakefile, GEM_NAME.gemspec,
-       and other supporting files and directories that can be used to  develop
-       a rubygem with that name.
-
-       Run  rake -T in the resulting project for a list of Rake tasks that can
-       be used to test and publish the gem to rubygems.org.
-
-       The generated project skeleton  can  be	customized  with  OPTIONS,  as
-       explained  below.  Note	that  these  options can also be specified via
-       Bundler's global configuration file using the following names:
-
-       o   gem.coc
-
-       o   gem.mit
-
-       o   gem.test
-
-
-
-OPTIONS
-       --exe or -b or --bin
-	      Specify that Bundler  should  create  a  binary  executable  (as
-	      exe/GEM_NAME) in the generated rubygem project. This binary will
-	      also be added to the GEM_NAME.gemspec manifest. This behavior is
-	      disabled by default.
-
-       --no-exe
-	      Do  not create a binary (overrides --exe specified in the global
-	      config).
-
-       --coc  Add a CODE_OF_CONDUCT.md file  to  the  root  of	the  generated
-	      project.	If  this  option is unspecified, an interactive prompt
-	      will be displayed and the answer	will  be  saved  in  Bundler's
-	      global config for future bundle gem use.
-
-       --no-coc
-	      Do not create a CODE_OF_CONDUCT.md (overrides --coc specified in
-	      the global config).
-
-       --ext  Add boilerplate for C extension code to the  generated  project.
-	      This behavior is disabled by default.
-
-       --no-ext
-	      Do  not  add  C extension code (overrides --ext specified in the
-	      global config).
-
-       --mit  Add an MIT license to a LICENSE.txt file in the root of the gen-
-	      erated project. Your name from the global git config is used for
-	      the copyright statement.	If  this  option  is  unspecified,  an
-	      interactive  prompt  will  be  displayed	and the answer will be
-	      saved in Bundler's global config for future bundle gem use.
-
-       --no-mit
-	      Do not create a LICENSE.txt (overrides --mit  specified  in  the
-	      global config).
-
-       -t, --test=minitest, --test=rspec
-	      Specify the test framework that Bundler should use when generat-
-	      ing the project. Acceptable values are minitest and  rspec.  The
-	      GEM_NAME.gemspec	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  bun-
-	      dle  gem	use.  If  no  option is specified, the default testing
-	      framework is RSpec.
-
-       -e, --edit[=EDITOR]
-	      Open the resulting GEM_NAME.gemspec in EDITOR,  or  the  default
-	      editor  if  not specified. The default is $BUNDLER_EDITOR, $VIS-
-	      UAL, or $EDITOR.
-
-SEE ALSO
-       o   bundle config(1) bundle-config.1.html
-
-
-
-
-
-
-				 January 2020			 BUNDLE-GEM(1)

data/man/bundle-info.1.txt

@@ -1,21 +0,0 @@
-BUNDLE-INFO(1)							BUNDLE-INFO(1)
-
-
-
-NAME
-       bundle-info - Show information for the given gem in your bundle
-
-SYNOPSIS
-       bundle info [GEM] [--path]
-
-DESCRIPTION
-       Print  the  basic  information about the provided GEM such as homepage,
-       version, path and summary.
-
-OPTIONS
-       --path Print the path of the given gem
-
-
-
-
-				 January 2020			BUNDLE-INFO(1)

data/man/bundle-init.1.txt

@@ -1,34 +0,0 @@
-BUNDLE-INIT(1)							BUNDLE-INIT(1)
-
-
-
-NAME
-       bundle-init - Generates a Gemfile into the current working directory
-
-SYNOPSIS
-       bundle init [--gemspec=FILE]
-
-DESCRIPTION
-       Init  generates a default [Gemfile(5)][Gemfile(5)] in the current work-
-       ing directory. When adding a [Gemfile(5)][Gemfile(5)] to a gem  with  a
-       gemspec,  the  --gemspec  option will automatically add each dependency
-       listed in the gemspec  file  to	the  newly  created  [Gemfile(5)][Gem-
-       file(5)].
-
-OPTIONS
-       --gemspec
-	      Use  the	specified  .gemspec  to  create  the [Gemfile(5)][Gem-
-	      file(5)]
-
-FILES
-       Included in the default [Gemfile(5)][Gemfile(5)] generated is the  line
-       #  frozen_string_literal:  true.  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.
-
-SEE ALSO
-       Gemfile(5) https://bundler.io/man/gemfile.5.html
-
-
-
-				 January 2020			BUNDLE-INIT(1)

data/man/bundle-inject.1.txt

@@ -1,32 +0,0 @@
-BUNDLE-INJECT(1)					      BUNDLE-INJECT(1)
-
-
-
-NAME
-       bundle-inject - Add named gem(s) with version requirements to Gemfile
-
-SYNOPSIS
-       bundle inject [GEM] [VERSION]
-
-DESCRIPTION
-       Adds  the  named gem(s) with their version requirements to the resolved
-       [Gemfile(5)][Gemfile(5)].
-
-       This command will add the gem to both your [Gemfile(5)][Gemfile(5)] and
-       Gemfile.lock if it isn't listed yet.
-
-       Example:
-
-
-
-	   bundle install
-	   bundle inject 'rack' '> 0'
-
-
-
-       This  will  inject the 'rack' gem with a version greater than 0 in your
-       [Gemfile(5)][Gemfile(5)] and Gemfile.lock
-
-
-
-				 January 2020		      BUNDLE-INJECT(1)