dadc7eb329
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.
56 lines
1.4 KiB
Nix
56 lines
1.4 KiB
Nix
{ stdenv, substituteAll }:
|
|
|
|
# Provides a facility to hook into rfkill changes.
|
|
#
|
|
# Exemplary usage:
|
|
#
|
|
# Add this package to udev.packages, e.g.:
|
|
# udev.packages = [ pkgs.rfkill_udev ];
|
|
#
|
|
# Add a hook script in the managed etc directory, e.g.:
|
|
# etc = [
|
|
# { source = pkgs.writeScript "rtfkill.hook" ''
|
|
# #!${pkgs.runtimeShell}
|
|
#
|
|
# if [ "$RFKILL_STATE" -eq "1" ]; then
|
|
# exec ${config.system.build.upstart}/sbin/initctl emit -n antenna-on
|
|
# else
|
|
# exec ${config.system.build.upstart}/sbin/initctl emit -n antenna-off
|
|
# fi
|
|
# '';
|
|
# target = "rfkill.hook";
|
|
# }
|
|
|
|
# Note: this package does not need the binaries
|
|
# in the rfkill package.
|
|
|
|
let
|
|
rfkillHook =
|
|
substituteAll {
|
|
inherit (stdenv) shell;
|
|
src = ./rfkill-hook.sh;
|
|
};
|
|
in stdenv.mkDerivation {
|
|
name = "rfkill-udev";
|
|
|
|
unpackPhase = "true";
|
|
dontBuild = true;
|
|
|
|
installPhase = ''
|
|
mkdir -p "$out/etc/udev/rules.d/";
|
|
cat > "$out/etc/udev/rules.d/90-rfkill.rules" << EOF
|
|
SUBSYSTEM=="rfkill", ATTR{type}=="wlan", RUN+="$out/bin/rfkill-hook.sh"
|
|
EOF
|
|
|
|
mkdir -p "$out/bin/";
|
|
cp ${rfkillHook} "$out/bin/rfkill-hook.sh"
|
|
chmod +x "$out/bin/rfkill-hook.sh";
|
|
'';
|
|
|
|
meta = {
|
|
homepage = http://wireless.kernel.org/en/users/Documentation/rfkill;
|
|
description = "Rules+hook for udev to catch rfkill state changes";
|
|
platforms = stdenv.lib.platforms.linux;
|
|
};
|
|
}
|