nix-gh/scripts/nix-profile.sh.in

#if test -z "$NIX_SET"; then

#    export NIX_SET=1

    NIX_LINKS=@localstatedir@/nix/links/current

    export PATH=$NIX_LINKS/bin:@prefix@/bin:$PATH

#    export LD_LIBRARY_PATH=$NIX_LINKS/lib:$LD_LIBRARY_PATH

    export LIBRARY_PATH=$NIX_LINKS/lib:$LIBRARY_PATH

    export C_INCLUDE_PATH=$NIX_LINKS/include:$C_INCLUDE_PATH
    export CPLUS_INCLUDE_PATH=$NIX_LINKS/include:$CPLUS_INCLUDE_PATH

    export PKG_CONFIG_PATH=$NIX_LINKS/lib/pkgconfig:$PKG_CONFIG_PATH

#    export MANPATH=$NIX_LINKS/man:$MANPATH

#fi
* Generate the scripts so that we can substitute the prefix etc. correctly. * Fixed nix-switch. 2003-07-13 20:58:03 +02:00			`#if test -z "$NIX_SET"; then`
* We no longer use nix-populate standalone, rather we use it as a build action for `system' packages (like system.fix) that have dependencies on all packages we want to activate. So the command sequence to switch to a new activation configuration of the system would be: $ fix -i .../fixdescriptors/system.fix ... system.fix -> 89cf4713b37cc66989304abeb9ea189f $ nix-switch 89cf4713b37cc66989304abeb9ea189f * A nix-profile.sh script that can be included in .bashrc. 2003-04-09 14:26:48 +02:00
* Generate the scripts so that we can substitute the prefix etc. correctly. * Fixed nix-switch. 2003-07-13 20:58:03 +02:00			`# export NIX_SET=1`
* We no longer use nix-populate standalone, rather we use it as a build action for `system' packages (like system.fix) that have dependencies on all packages we want to activate. So the command sequence to switch to a new activation configuration of the system would be: $ fix -i .../fixdescriptors/system.fix ... system.fix -> 89cf4713b37cc66989304abeb9ea189f $ nix-switch 89cf4713b37cc66989304abeb9ea189f * A nix-profile.sh script that can be included in .bashrc. 2003-04-09 14:26:48 +02:00
* Generate the scripts so that we can substitute the prefix etc. correctly. * Fixed nix-switch. 2003-07-13 20:58:03 +02:00			`NIX_LINKS=@localstatedir@/nix/links/current`
* We no longer use nix-populate standalone, rather we use it as a build action for `system' packages (like system.fix) that have dependencies on all packages we want to activate. So the command sequence to switch to a new activation configuration of the system would be: $ fix -i .../fixdescriptors/system.fix ... system.fix -> 89cf4713b37cc66989304abeb9ea189f $ nix-switch 89cf4713b37cc66989304abeb9ea189f * A nix-profile.sh script that can be included in .bashrc. 2003-04-09 14:26:48 +02:00
* Generate the scripts so that we can substitute the prefix etc. correctly. * Fixed nix-switch. 2003-07-13 20:58:03 +02:00			`export PATH=$NIX_LINKS/bin:@prefix@/bin:$PATH`
* We no longer use nix-populate standalone, rather we use it as a build action for `system' packages (like system.fix) that have dependencies on all packages we want to activate. So the command sequence to switch to a new activation configuration of the system would be: $ fix -i .../fixdescriptors/system.fix ... system.fix -> 89cf4713b37cc66989304abeb9ea189f $ nix-switch 89cf4713b37cc66989304abeb9ea189f * A nix-profile.sh script that can be included in .bashrc. 2003-04-09 14:26:48 +02:00
* Do not set LD_LIBRARY_PATH; it breaks many things. E.g., SuSE's ssh dynamically links against libdb4 (?!), due to LD_LIBRARY_PATH it picks up our libdb4 instead of SuSE's libdb4, but our libdb4 uses another glibc so loading barfs. Instead, all packages should use rpaths to store library locations in executables/libraries. The disadvantage is that overriding rpaths is harder. (It is possible by invoking the dynamic linker directly, e.g., `/lib/ld-linux.so.2 --ignore-path LIST program args...' to ignore the rpath for the libraries in LIST). It would be better to use DT_RUNPATH, which is consulted by the dynamic linker after LD_LIBRARY_PATH but before ld.so.cache and the system directories. 2003-07-28 18:07:01 +02:00			`# export LD_LIBRARY_PATH=$NIX_LINKS/lib:$LD_LIBRARY_PATH`
* We no longer use nix-populate standalone, rather we use it as a build action for `system' packages (like system.fix) that have dependencies on all packages we want to activate. So the command sequence to switch to a new activation configuration of the system would be: $ fix -i .../fixdescriptors/system.fix ... system.fix -> 89cf4713b37cc66989304abeb9ea189f $ nix-switch 89cf4713b37cc66989304abeb9ea189f * A nix-profile.sh script that can be included in .bashrc. 2003-04-09 14:26:48 +02:00
			`export LIBRARY_PATH=$NIX_LINKS/lib:$LIBRARY_PATH`

			`export C_INCLUDE_PATH=$NIX_LINKS/include:$C_INCLUDE_PATH`
* Set CPLUS_INCLUDE_PATH as well as C_INCLUDE_PATH. Otherwise g++ won't see header files under Nix control. 2003-06-18 14:35:32 +02:00			`export CPLUS_INCLUDE_PATH=$NIX_LINKS/include:$CPLUS_INCLUDE_PATH`
* We no longer use nix-populate standalone, rather we use it as a build action for `system' packages (like system.fix) that have dependencies on all packages we want to activate. So the command sequence to switch to a new activation configuration of the system would be: $ fix -i .../fixdescriptors/system.fix ... system.fix -> 89cf4713b37cc66989304abeb9ea189f $ nix-switch 89cf4713b37cc66989304abeb9ea189f * A nix-profile.sh script that can be included in .bashrc. 2003-04-09 14:26:48 +02:00
* Set MANPATH and PKG_CONFIG_PATH. 2003-05-30 13:49:06 +02:00			`export PKG_CONFIG_PATH=$NIX_LINKS/lib/pkgconfig:$PKG_CONFIG_PATH`

* Don't set MANPATH. It's not necessary. 2003-05-30 17:17:40 +02:00			`# export MANPATH=$NIX_LINKS/man:$MANPATH`
* Set MANPATH and PKG_CONFIG_PATH. 2003-05-30 13:49:06 +02:00
* Generate the scripts so that we can substitute the prefix etc. correctly. * Fixed nix-switch. 2003-07-13 20:58:03 +02:00			`#fi`