Revert 11339c91. Don't use virtualenv to build packages.

fpm and virtualenv don't play nicely together.  Under virtualenv, fpm
ends up building Python packages that include the files under their
virtualenv paths.  This is not what we want.  Refs #5175.

diff --git a/jenkins/run-build-packages.sh b/jenkins/run-build-packages.sh
index cdf1d17a251b6b5fa0cfbb43d0b102ae92e592e4..1dae4bcd783e9ebf905c82ad08c8ab71ab2a1aef 100755 (executable)
--- a/jenkins/run-build-packages.sh
+++ b/jenkins/run-build-packages.sh
@@ -85,14 +85,6 @@ if [[ "$DEBUG" != 0 ]]; then
   echo "Workspace is $WORKSPACE"
 fi
 
-# We need a recent setuptools. Older ones replace + with - in our
-# version numbers, making them non-PEP-440-compliant and
-# non-uploadable.
-VENV=$(mktemp -d)
-echo "Using virtualenv $VENV"
-virtualenv "$VENV"
-. "$VENV/bin/activate"
-
 version_from_git() {
   # Generates a version number from the git log for the current working
   # directory, and writes it to stdout.
@@ -485,8 +477,7 @@ else
   fi
 fi
 
-# clean up temporary GOPATH and VENV
+# clean up temporary GOPATH
 rm -rf "$GOPATH"
-rm -rf "$VENV"
 
 exit $EXITCODE