diff options
author | André Arko <mail@arko.net> | 2015-07-21 20:17:37 -0700 |
---|---|---|
committer | André Arko <mail@arko.net> | 2015-07-21 20:17:37 -0700 |
commit | 492c87a7a4ba01aea72c3206b126c23a1c39167b (patch) | |
tree | 745341af5b0023e2ecb2599d7f7d66a22ac1a59f | |
parent | dae5ba819e1dfd3ff6019acecdfb97274251487f (diff) | |
parent | edff91d0d8feff7ed410490574513c214823d2c4 (diff) | |
download | bundler-492c87a7a4ba01aea72c3206b126c23a1c39167b.tar.gz |
Merge pull request #3867 from mattbrictson/bin-exe-path
bin should be exe in `alias dbundle` instructions
-rw-r--r-- | DEVELOPMENT.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/DEVELOPMENT.md b/DEVELOPMENT.md index 46b519d95f..464dfec317 100644 --- a/DEVELOPMENT.md +++ b/DEVELOPMENT.md @@ -29,7 +29,7 @@ Bundler doesn't use a Gemfile to list development dependencies, because when we 3. 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/bin/bundle' + $ alias dbundle='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. |