nixpkgs/pkgs/misc/my-env/loadenv.sh

#!@shell@

OLDPATH="$PATH"
OLDTZ="$TZ"
OLD_http_proxy="$http_proxy"
OLD_ftp_proxy="$http_proxy"
source @myenvpath@

PATH="$PATH:$OLDPATH"
export PS1="\n@name@:[\u@\h:\w]\$ "
export NIX_MYENV_NAME="@name@"
export buildInputs
export TZ="$OLDTZ"
export http_proxy="$OLD_http_proxy"
export ftp_proxy="$OLD_ftp_proxy"

if test $# -gt 0; then
    exec "$@"
else
    exec @shell@
fi
Fixing my-env to get NIX_CFLAGS_COMPILE and so on Yes, I still use my-env. I tested that it works on 16.03. 2016-03-09 03:40:17 -08:00			`#!@shell@`
Updating the script of loading myEnv environments, for something close to what I was using. It sets a fixed PS1, maybe breaking someone's taste, though. But I find it easier to use. svn path=/nixpkgs/trunk/; revision=33304 2012-03-20 11:49:44 -07:00
			`OLDPATH="$PATH"`
			`OLDTZ="$TZ"`
my-env: Preserve http_proxy and ftp_proxy variables There are few build scripts which set them to `nodtd.invalid` to disable downloading files by buildscript. But for user environment we should restore original values 2014-07-12 12:51:28 -07:00			`OLD_http_proxy="$http_proxy"`
			`OLD_ftp_proxy="$http_proxy"`
Updating the script of loading myEnv environments, for something close to what I was using. It sets a fixed PS1, maybe breaking someone's taste, though. But I find it easier to use. svn path=/nixpkgs/trunk/; revision=33304 2012-03-20 11:49:44 -07:00			`source @myenvpath@`

			`PATH="$PATH:$OLDPATH"`
			`export PS1="\n@name@:[\u@\h:\w]\$ "`
Add `NIX_MYENV_NAME` environment variable in `myEnvFun` 2014-06-29 05:45:20 -07:00			`export NIX_MYENV_NAME="@name@"`
Updating the script of loading myEnv environments, for something close to what I was using. It sets a fixed PS1, maybe breaking someone's taste, though. But I find it easier to use. svn path=/nixpkgs/trunk/; revision=33304 2012-03-20 11:49:44 -07:00			`export buildInputs`
			`export TZ="$OLDTZ"`
my-env: Preserve http_proxy and ftp_proxy variables There are few build scripts which set them to `nodtd.invalid` to disable downloading files by buildscript. But for user environment we should restore original values 2014-07-12 12:51:28 -07:00			`export http_proxy="$OLD_http_proxy"`
			`export ftp_proxy="$OLD_ftp_proxy"`
Updating the script of loading myEnv environments, for something close to what I was using. It sets a fixed PS1, maybe breaking someone's taste, though. But I find it easier to use. svn path=/nixpkgs/trunk/; revision=33304 2012-03-20 11:49:44 -07:00
my-env: Support for running command directly by load-env-xxx script First I don't think there is a reason to run shell as a child of load-env-xxx script and not to just exec into it. Also it's often useful to just run a command inside the environment load-env-xxx command --args Closes #3254 2014-07-12 06:32:28 -07:00			`if test $# -gt 0; then`
			`exec "$@"`
			`else`
			`exec @shell@`
			`fi`
Add cleanupCmds option to pkgs.myEnvFun This option allows the user to specify commands to run when the shell exits. This can be used to cleanup operations done in `extraCmds'. Signed-off-by: Moritz Ulrich <moritz@tarn-vedra.de> 2013-04-13 10:10:50 -07:00