Do not build the fabric peer during vagrant provision

Building the peer during vagrant provisioning takes
extra time. We can't be sure the user even wants to
build the peer.  They may be trying to perform some
other task (such as work on the SDK), in which case
we are wasting their time.  Therefore, remove peer
building from the critical path of provisioning
and allow the user to make their own decision.  This
has the nice benefit of making the provisioning
process nice and snappy.

Change-Id: I82f120faceeff8d8de08f064d4a6fd911eec65d9
Signed-off-by: Greg Haskins <[email protected]>

Author: ghaskins

devenv/setup.sh

@@ -78,9 +78,12 @@ PATH=$GOROOT/bin:$GOPATH/bin:$PATH
 sudo mkdir -p /var/hyperledger
 sudo chown -R vagrant:vagrant /var/hyperledger
 
-# Build the actual hyperledger peer (must be done before chown below)
+# clean any previous builds as they may have image/.dummy files without
+# the backing docker images (since we are, by definition, rebuilding the
+# filesystem) and then ensure we have a fresh set of our go-tools.
+# NOTE: This must be done before the chown below
 cd $GOPATH/src/github.com/hyperledger/fabric
-make clean peer gotools
+make clean gotools
 
 # Ensure permissions are set for GOPATH
 sudo chown -R vagrant:vagrant $GOPATH