Don't reset HOME in redstack
Currently redstack resets HOME as the first thing that it does. It isn't particlularly apparent why this is required; it may have been needed in a long ago time when paths to thing were trove-integrations/scripts relative but they aren't now. Change-Id: If0f7329ea37f6d92f10b815c7a96eaee97d8b6d4 Closes-Bug: #1552048
This commit is contained in:
parent
8dc1948a3a
commit
c8020fff45
|
@ -173,16 +173,8 @@ function pkg_update () {
|
|||
}
|
||||
|
||||
function set_home_dir() {
|
||||
self="${0#./}"
|
||||
base="${self%/*}"
|
||||
current=`pwd`
|
||||
if [ "$base" = "$self" ] ; then
|
||||
HOME="$current/"
|
||||
elif [[ $base =~ ^/ ]]; then
|
||||
HOME="$base/"
|
||||
else
|
||||
HOME="$current/$base/"
|
||||
fi
|
||||
exclaim "set_home_dir has been nooped."
|
||||
exit 1
|
||||
}
|
||||
|
||||
function set_http_proxy() {
|
||||
|
@ -1240,7 +1232,7 @@ fi
|
|||
# Set this to exit immediately on error
|
||||
set -o errexit
|
||||
|
||||
set_home_dir
|
||||
# set_home_dir
|
||||
set_http_proxy
|
||||
set_trove_plugin_vars false
|
||||
|
||||
|
|
Loading…
Reference in New Issue