aboutsummaryrefslogtreecommitdiffstats
path: root/lib/bundler/runtime.rb
Commit message (Collapse)AuthorAgeFilesLines
* Resolve for specific platformsSamuel Giddins2016-08-251-1/+2
|
* Rename all BUNDLE_ORIG_* env to BUNDLER_ORIG*Andre Arko2016-08-101-1/+1
| | | | | | | | | | | | Any enviroment variable that starts with BUNDLE_ will be treated as a configurationg setting, printed by `bundle config`, and made available internally via `Bundler.settings`. The ORIG_* environment variables are actually just internal housekeeping to enable us to provide clean non-bundled environments, and so they shouldn't show up as settings. This change to the environment variable names makes sure it is still clear where they are coming from, but no longer surfaces them via config/settings.
* Remove Bundler::EnvironmentSamuel Giddins2016-08-031-1/+24
|
* fix gemspec cachingSamuel Giddins2016-06-041-8/+1
|
* Fix the combination of gem :require and env or install_ifBrian Hawley2016-05-241-3/+3
| | | | | | | If you guard the installation of a gem with env or install_if, and that gem declaration has a :require option specified, it tried to require the gem even though it hadn't been installed. It looks like a spot was missed when the env command was added in the first place.
* Auto merge of #4471 - grzuy:remove_unused_method, r=indirectHomu2016-05-161-8/+0
|\ | | | | | | | | | | | | | | | | | | Cleans up unused Runtime#dependencies_for method Hi! I was checking out things in the code and couldn't find any existent usage of this method. I might be missing something but opening the PR just in case. The method seems to be publicly accessible if someone goes `Bundler.load.dependencies_for(...)` e.g., but i am assuming that's not something "officially supported" anyways?
| * Removes unused Runtime#dependencies_for methodGonzalo2016-04-271-8/+0
| |
* | [Runtime] Keep load paths within a single spec properly sortedSamuel Giddins2016-04-291-1/+1
| |
* | [Runtime] Fix the ordering of the load path when there are dependenciesSamuel Giddins2016-04-291-12/+10
|/ | | | It was previously getting reversed
* [LockfileParser] Rename attribute to sectionSamuel Giddins2016-04-181-1/+1
|
* Generically preserve new attributes in lockfileSamuel Giddins2016-04-181-1/+1
|
* Prevent recursive `bundle package` loop with multiple gemspecsJames Wen2016-04-141-5/+5
| | | | - Fixes #4430
* Prevent endless recursive copy for `bundle package --all` andJames Wen2016-03-251-1/+2
| | | | | | differently named gemspecs and gems - Fixes #4392
* Auto merge of #4268 - Elffers:hhh_fix_ruby-I, r=indirectHomu2016-02-111-1/+11
|\ | | | | | | | | | | | | | | | | | | Place bundler loaded gems after -I and RUBYLIB Previously, gems were being placed at the front of the LOAD_PATH. This meant you couldn't override a gem by setting -I or RUBYLIB. This patch places -I and RUBYLIB in front of loaded gems and matches the behavior in RubyGems.
| * Wrap Gem method as rubygems integrationHsing-Hui Hsu2016-02-071-1/+1
| |
| * Place bundler loaded gems after -I and RUBYLIBHsing-Hui Hsu2016-02-021-1/+11
| | | | | | | | | | | | | | | | Previously, gems were being placed at the front of the LOAD_PATH. This meant you couldn't override a gem by setting -I or RUBYLIB. This patch places -I and RUBYLIB in front of loaded gems and matches the behavior in RubyGems.
* | [Exec] Avoid loading the definition before exec-ingSamuel Giddins2016-02-011-14/+1
|/
* Compatibility with frozen string literalsSamuel Giddins2016-01-311-0/+1
|
* [RuboCop] Fix Style/MutableConstantSamuel Giddins2016-01-311-1/+1
|
* [RuboCop] Address Style/GuardClauseSamuel Giddins2016-01-311-5/+4
|
* Use SharedHelpers#filesystem_access in bundle clean for a friendlier error ↵James Wen2015-12-181-2/+10
| | | | message for denied permissions
* Fix broken `bundle package --all` command and prevent endless recursive copyJames Wen2015-12-151-0/+8
| | | | | - Only cache path-sourced gem specs that are not bundler and not the gem specified by the gemspec in the main directory the command is being executed from
* Auto merge of #4124 - bundler:seg-rubocop, r=indirectHomu2015-11-271-1/+1
|\ | | | | | | More rubocop_todo cleanup
| * [RuboCop] Enable Style/AndOrSamuel Giddins2015-11-261-1/+1
| |
* | Use exe instead of bin for BUNDLE_BIN_PATH fallbackJay Mundrawala2015-10-191-1/+1
|/
* runtime: avoid cleaning up extensions directorySimon Eskildsen2015-10-031-1/+1
|
* Wrap filesystem operations with #filesystem_accessAgis Anastasopoulos2015-09-271-2/+6
|
* Removes duplication from bundle clean commandPhil Nash2015-09-261-36/+23
|
* Handle errors when requiring gems gracefullyAgis-2015-08-291-1/+7
| | | | Fixes #3960.
* Fix Style/ParenthesesAroundConditionVictor Koronen2015-08-141-1/+1
|
* [RuboCop] Update to 0.33.0Samuel E. Giddins2015-08-071-3/+3
|
* Fix Style/AliasErick Sasse2015-07-231-1/+1
|
* Fix Style/SpaceInsideBlockBracesAndre Arko2015-07-181-8/+8
| | | | closes #3850
* [RuboCop] Enable Style/StringLiteralsSamuel E. Giddins2015-07-151-12/+12
|
* [RuboCop] Enable Style/SymbolProcSamuel E. Giddins2015-07-151-2/+2
|
* [RuboCop] Enable Style/EmptyLinesSamuel E. Giddins2015-07-151-1/+0
|
* avoid altering BUNDLED WITH during implicit locksAndre Arko2015-06-081-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | When either `bundle check` is run, or any application requires the `bundler/setup` file, Bundler will automatically check whether it is possible to lock the Bundle. During the lock process, Bundler updates the lock if the implicit locking changes the lock file. Starting with the 1.10 release, Bundler includes a lockfile section named BUNDLED WITH that includes the version of Bundler that generated the lockfile. In order to minimize git churn, and guarantee that the lockfile will only be changed when the user runs an explicit Bundler command, Bundler will now only add or update the BUNDLED WITH section during commands where the user asks for changes to the lock. This includes, but is not limited to, `install`, `update`, `lock`, and `package`. Running the `check` command or loading an application that uses Bundler will still now add or update the BUNDLED WITH section if, and only if, the lockfile has also changed for a different reason (such as a gem being updated). Simply using an application, by running `bundle exec` commands or by running `bin/rails` and the like, will not change the lockfile. As a result, the intended workflow with the BUNDLED WITH section is now slightly different than it was before: 1. When running `bundle install`, Bundler will update the version in the lockfile if newer than the version present. 2. Then, check in the lockfile change, exactly as you would after running install to change any other gem version. 3. Older versions of Bundler will not change the number in the lock, but will warn the user that they are out of date. refs bundler/bundler-features#80 refs #3697
* Merge tag 'v1.9.4'Andre Arko2015-04-131-3/+0
| | | | | | | | Version 1.9.4 Conflicts: lib/bundler/installer.rb lib/bundler/match_platform.rb lib/bundler/source/rubygems.rb
* allow cache path to be configuredAndre Arko2015-01-251-17/+12
| | | | | | | this adds `package —cache-path`, supports `config cache_path foo`, and honors the BUNDLE_CACHE_PATH environment variable. closes #3351
* share bundle env setup between exec and RuntimeAndre Arko2015-01-191-16/+1
| | | | | this means we only have to maintain setting up Bundler environment variables in one place
* implement all_platforms options for cache/packageCody Cutrer2014-12-231-0/+1
| | | | so that a single cache directory can be used with multiple ruby versions
* Report exceptions while requiringAndre Arko2014-12-091-0/+3
|
* Merge pull request #3195 from Intrepidd/patch-1Andre Arko2014-10-021-7/+5
|\ | | | | | | Don't swallow LoadErrors when requiring a dashed gem
| * Don't swallow LoadErrors when requiring a dashed gemAdrien2014-10-021-3/+2
|/ | | | | | | | | | | | This looks like #1807 when raising a LoadError in a required gem, bundler will rescue it to try and see if it came from his own namespaced require or from the required file. If it comes from the dashed require it will re-raise the original exception in case the gem was dashed but the first require was ok but raised a LoadError after. However, the exception is swallowed if we require a dashed gem without the proper file name, for example gem name : 'foo-bar' and file architecture : 'foo/bar.rb' This PR raise the exception back in case it really comes from inside the namespaced file.
* Encapsulate Definition#sources.Andre Arko2014-07-301-1/+1
|
* use File.exist? instead of File.exists?SHIBATA Hiroshi2014-02-091-6/+6
|
* --path changes directory where 'vendor/cache' is createdGabriel Jaldon2013-12-221-12/+15
|
* Less confusing message in 'use bundle exec' error message.Xavier Shay2013-08-061-1/+2
|
* Merge pull request #2019 from luismreis/masterAndre Arko2013-08-041-0/+1
|\ | | | | | | Properly handle missing binary libraries.
| * Handle error messages caused by missing binary libraries.Luis Reis2012-07-081-0/+1
| |
generated by cgit v1.2.3 (git 2.39.1) at 2024-09-25 03:29:52 +0000