summaryrefslogtreecommitdiff
path: root/DEVELOPMENT.md
diff options
context:
space:
mode:
authorSamuel Giddins <segiddins@segiddins.me>2016-12-26 20:32:03 -0600
committerSamuel Giddins <segiddins@segiddins.me>2016-12-26 20:32:03 -0600
commitf8534729342feb1314dba9da46f457f8e5247e2f (patch)
tree1eadda03e9f3069947bdc61999e2340c0b2f1a03 /DEVELOPMENT.md
parentb361db92def2ad0634f2dc43216ac62242216d9f (diff)
downloadbundler-f8534729342feb1314dba9da46f457f8e5247e2f.tar.gz
[PostitTrampoline] Rename env varsseg-platform-docs
Diffstat (limited to 'DEVELOPMENT.md')
-rw-r--r--DEVELOPMENT.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/DEVELOPMENT.md b/DEVELOPMENT.md
index 67e1527677..97e764dea9 100644
--- a/DEVELOPMENT.md
+++ b/DEVELOPMENT.md
@@ -36,9 +36,9 @@ Bundler doesn't use a Gemfile to list development dependencies, because when we
4. Set up a shell alias to run Bundler from your clone, e.g. a Bash alias:
- $ alias dbundle='BUNDLE_DISABLE_POSTIT=1 ruby -I /path/to/bundler/lib /path/to/bundler/exe/bundle'
+ $ alias dbundle='BUNDLE_TRAMPOLINE_DISABLE=1 ruby -I /path/to/bundler/lib /path/to/bundler/exe/bundle'
- The `BUNDLE_DISABLE_POSTIT` environment variable ensures that the version of Bundler in `/path/to/bundler/lib` will be used. Without that environment setting, Bundler will automatically download, install, and run the version of Bundler listed in `Gemfile.lock`. With that set up, you can test changes you've made to Bundler by running `dbundle`, without interfering with the regular `bundle` command.
+ The `BUNDLE_TRAMPOLINE_DISABLE` environment variable ensures that the version of Bundler in `/path/to/bundler/lib` will be used. Without that environment setting, Bundler will automatically download, install, and run the version of Bundler listed in `Gemfile.lock`. With that set up, you can test changes you've made to Bundler by running `dbundle`, without interfering with the regular `bundle` command.
To dive into the code with Pry: `RUBYOPT=-rpry dbundle` to require pry and then run commands.