nixpkgs/pkgs/tools/misc/zsh-autoenv/default.nix
Jörg Thalheim dadc7eb329
treewide: use runtimeShell instead of stdenv.shell whenever possible
Whenever we create scripts that are installed to $out, we must use runtimeShell
in order to get the shell that can be executed on the machine we create the
package for. This is relevant for cross-compiling. The only use case for
stdenv.shell are scripts that are executed as part of the build system.
Usages in checkPhase are borderline however to decrease the likelyhood
of people copying the wrong examples, I decided to use runtimeShell as well.
2019-02-26 14:10:49 +00:00

41 lines
1.2 KiB
Nix

{ stdenv, fetchFromGitHub, runtimeShell }:
stdenv.mkDerivation rec {
name = "zsh-autoenv-${version}";
version = "2017-12-16";
src = fetchFromGitHub {
owner = "Tarrasch";
repo = "zsh-autoenv";
rev = "2c8cfbcea8e7286649840d7ec98d7e9d5e1d45a0";
sha256 = "004svkfzhc3ab6q2qvwzgj36wvicg5bs8d2gcibx6adq042di7zj";
};
buildPhase = ":";
installPhase = ''
mkdir -p $out/{bin,share}
cp -R $src $out/share/zsh-autoenv
cat <<SCRIPT > $out/bin/zsh-autoenv-share
#!${runtimeShell}
# Run this script to find the fzf shared folder where all the shell
# integration scripts are living.
echo $out/share/zsh-autoenv
SCRIPT
chmod +x $out/bin/zsh-autoenv-share
'';
meta = with stdenv.lib; {
description = "Automatically sources whitelisted .autoenv.zsh files";
longDescription = ''
zsh-autoenv automatically sources (known/whitelisted)
.autoenv.zsh files, typically used in project root directories.
It handles "enter" and "leave" events, nesting, and stashing of
variables (overwriting and restoring).
'';
homepage = https://github.com/Tarrasch/zsh-autoenv;
platforms = stdenv.lib.platforms.all;
};
}