summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorAndre Arko <andre@arko.net>2016-06-24 16:27:13 -0700
committerAndre Arko <andre@arko.net>2016-06-24 16:51:05 -0700
commitc90a6c162a10ce9fa3055da0af17be224af61008 (patch)
tree210c93ea2121c36d8e4d11ac82267139d33d5854
parentdca6d26833ddd9d9de658bef7274c8fa21014c44 (diff)
downloadbundler-aa-dbundle-no-trampoline.tar.gz
disable trampoline in dbundleaa-dbundle-no-trampoline
-rw-r--r--DEVELOPMENT.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/DEVELOPMENT.md b/DEVELOPMENT.md
index 8676904244..bc0a2666a6 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='ruby -I /path/to/bundler/lib /path/to/bundler/exe/bundle'
+ $ alias dbundle='BUNDLE_DISABLE_POSTIT=1 ruby -I /path/to/bundler/lib /path/to/bundler/exe/bundle'
- 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_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.
# Submitting Pull Requests