From 1556cebcf8b4b601177cb6dc1283603cace5b028 Mon Sep 17 00:00:00 2001 From: Greg Anderson Date: Sat, 4 Jun 2016 12:29:32 -0700 Subject: [PATCH] Clarify the alternative solution. --- README.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index 6479295..747c6ef 100644 --- a/README.md +++ b/README.md @@ -44,8 +44,9 @@ Composer will also load Composer Plugins from the "global" Composer project. Thi ## Alternative Solutions -The cgr script maintains the convenience of automatically managing the global installation location for you; however, if this is not desired, you may simply set: +The cgr script maintains the convenience of automatically managing the global installation location for you; however, if this is not desired, you may simply run commands similar to: -`export COMPOSER_BIN_DIR=$HOME/bin` +`COMPOSER_BIN_DIR=$HOME/bin composer require org/project:~1.0` + +If you go this route, you will need to set up your install location manually using `mkdir` and `cd` as necessary prior to running `composer require`. You cannot simply set COMPOSER_BIN_DIR globally, as doing this would cause the binaries from local projects to be installed into your global bin directory, which would, of course, not be desirable. -Then, use `composer require` rather than `composer global require` to install projects. If you go this route, you will need to set up your install location manually using `mkdir` and `cd` as necessary prior to running `composer require`.