File: C:/Ruby27-x64/share/ri/2.7.0/system/Bundler/Installer/run-i.ri
U:RDoc::AnyMethod[iI"run:ETI"Bundler::Installer#run;TF:publico:RDoc::Markup::Document:@parts[o:RDoc::Markup::Paragraph; [I"8Runs the install procedures for a specific Gemfile.;To:RDoc::Markup::BlankLine o;
; [ I"LFirstly, this method will check to see if `Bundler.bundle_path` exists ;TI"Qand if not then Bundler will create the directory. This is usually the same ;TI"Dlocation as RubyGems which typically is the `~/.gem` directory ;TI"unless other specified.;T@o;
; [I"HSecondly, it checks if Bundler has been configured to be "frozen". ;TI"MFrozen ensures that the Gemfile and the Gemfile.lock file are matching. ;TI"UThis stops a situation where a developer may update the Gemfile but may not run ;TI"Y`bundle install`, which leads to the Gemfile.lock file not being correctly updated. ;TI"LIf this file is not correctly updated then any other developer running ;TI"D`bundle install` will potentially not install the correct gems.;T@o;
; [I"UThirdly, Bundler checks if there are any dependencies specified in the Gemfile. ;TI"[If there are no dependencies specified then Bundler returns a warning message stating ;TI" so and this method returns.;T@o;
; [ I"DFourthly, Bundler checks if the Gemfile.lock exists, and if so ;TI"Uthen proceeds to set up a definition based on the Gemfile and the Gemfile.lock. ;TI"PDuring this step Bundler will also download information about any new gems ;TI"Mthat are not in the Gemfile.lock and resolve any dependencies if needed.;T@o;
; [ I"]Fifthly, Bundler resolves the dependencies either through a cache of gems or by remote. ;TI"\This then leads into the gems being installed, along with stubs for their executables, ;TI"]but only if the --binstubs option has been passed or Bundler.options[:bin] has been set ;TI"
earlier.;T@o;
; [I"aSixthly, a new Gemfile.lock is created from the installed gems to ensure that the next time ;TI"Wthat a user runs `bundle install` they will receive any updates from this process.;T@o;
; [I"^Finally, if the user has specified the standalone flag, Bundler will generate the needed ;TI"_require paths and save them in a `setup.rb` file. See `bundle standalone --help` for more ;TI"information.;T:
@fileI"lib/bundler/installer.rb;T:0@omit_headings_from_table_of_contents_below000[ I"(options);T@7FI"Installer;TcRDoc::NormalClass00