nixpkgs/pkgs/by-name/ud/udevCheckHook/package.nix

{
  lib,
  makeSetupHook,
  systemdMinimal,
  stdenv,
}:
let
  # udev rules can only be checked if systemd (specifically, 'udevadm') can be executed on build platform
  # If cross-compiling linux -> non-linux, udev rules are still checked, even if they end up being unused.
  # This is not a problem:
  # - If there are no udev rules, the hook is a noop
  # - If the udev rules are broken, they should be flagged as such
  # - if rules are not needed on a target platform where they are broken, they should be deleted from package output
  applyHook = lib.meta.availableOn stdenv.buildPlatform systemdMinimal;
in
makeSetupHook {
  name = "udev-check-hook";
  substitutions = {
    udevadm = if applyHook then lib.getExe' systemdMinimal "udevadm" else "";
  };
  meta = {
    description = "Check validity of udev rules in outputs";
    maintainers = with lib.maintainers; [ grimmauld ];
  };
} ./hook.sh
udevCheckHook: init Usage: ```nix nativeBuildInputs = [ udevCheckHook ]; doInstallCheck = true; ``` This hook executes `udevadm verify --resolve-names=never --no-style` on all outputs that have `/etc/udev/rules.d`. This us a logical part of #404323 to check packages that supply udev rules. Note this hook introduces a dependency on `systemdMinimal`, meaning this can't check systemdMinimal or its dependencies. 2025-05-16 15:37:55 +02:00			`{`
			`lib,`
			`makeSetupHook,`
			`systemdMinimal,`
udevCheckHook: guard platform It is technically possible to guard all udevCheckHook usages behind `lib.optionals (lib.meta.availableOn stdenv.buildPlatform systemdMinimal)`. However, doing this is hard to read, clunky, and hard to discover. Not doing such a guard would mean cross-compilation darwin -> linux breaks. The workaround here is to just accept any udev rules if they can't be properly checked. 2025-05-21 13:44:58 +02:00			`stdenv,`
udevCheckHook: init Usage: ```nix nativeBuildInputs = [ udevCheckHook ]; doInstallCheck = true; ``` This hook executes `udevadm verify --resolve-names=never --no-style` on all outputs that have `/etc/udev/rules.d`. This us a logical part of #404323 to check packages that supply udev rules. Note this hook introduces a dependency on `systemdMinimal`, meaning this can't check systemdMinimal or its dependencies. 2025-05-16 15:37:55 +02:00			`}:`
udevCheckHook: guard platform It is technically possible to guard all udevCheckHook usages behind `lib.optionals (lib.meta.availableOn stdenv.buildPlatform systemdMinimal)`. However, doing this is hard to read, clunky, and hard to discover. Not doing such a guard would mean cross-compilation darwin -> linux breaks. The workaround here is to just accept any udev rules if they can't be properly checked. 2025-05-21 13:44:58 +02:00			`let`
			`# udev rules can only be checked if systemd (specifically, 'udevadm') can be executed on build platform`
udevCheckHook: remove broken cross-compilation check 2025-05-31 18:08:09 +02:00			`# If cross-compiling linux -> non-linux, udev rules are still checked, even if they end up being unused.`
			`# This is not a problem:`
			`# - If there are no udev rules, the hook is a noop`
			`# - If the udev rules are broken, they should be flagged as such`
			`# - if rules are not needed on a target platform where they are broken, they should be deleted from package output`
			`applyHook = lib.meta.availableOn stdenv.buildPlatform systemdMinimal;`
udevCheckHook: guard platform It is technically possible to guard all udevCheckHook usages behind `lib.optionals (lib.meta.availableOn stdenv.buildPlatform systemdMinimal)`. However, doing this is hard to read, clunky, and hard to discover. Not doing such a guard would mean cross-compilation darwin -> linux breaks. The workaround here is to just accept any udev rules if they can't be properly checked. 2025-05-21 13:44:58 +02:00			`in`
udevCheckHook: init Usage: ```nix nativeBuildInputs = [ udevCheckHook ]; doInstallCheck = true; ``` This hook executes `udevadm verify --resolve-names=never --no-style` on all outputs that have `/etc/udev/rules.d`. This us a logical part of #404323 to check packages that supply udev rules. Note this hook introduces a dependency on `systemdMinimal`, meaning this can't check systemdMinimal or its dependencies. 2025-05-16 15:37:55 +02:00			`makeSetupHook {`
			`name = "udev-check-hook";`
			`substitutions = {`
udevCheckHook: guard platform It is technically possible to guard all udevCheckHook usages behind `lib.optionals (lib.meta.availableOn stdenv.buildPlatform systemdMinimal)`. However, doing this is hard to read, clunky, and hard to discover. Not doing such a guard would mean cross-compilation darwin -> linux breaks. The workaround here is to just accept any udev rules if they can't be properly checked. 2025-05-21 13:44:58 +02:00			`udevadm = if applyHook then lib.getExe' systemdMinimal "udevadm" else "";`
udevCheckHook: init Usage: ```nix nativeBuildInputs = [ udevCheckHook ]; doInstallCheck = true; ``` This hook executes `udevadm verify --resolve-names=never --no-style` on all outputs that have `/etc/udev/rules.d`. This us a logical part of #404323 to check packages that supply udev rules. Note this hook introduces a dependency on `systemdMinimal`, meaning this can't check systemdMinimal or its dependencies. 2025-05-16 15:37:55 +02:00			`};`
			`meta = {`
treewide: conform descriptions to the standards 2025-07-23 04:23:40 +00:00			`description = "Check validity of udev rules in outputs";`
udevCheckHook: init Usage: ```nix nativeBuildInputs = [ udevCheckHook ]; doInstallCheck = true; ``` This hook executes `udevadm verify --resolve-names=never --no-style` on all outputs that have `/etc/udev/rules.d`. This us a logical part of #404323 to check packages that supply udev rules. Note this hook introduces a dependency on `systemdMinimal`, meaning this can't check systemdMinimal or its dependencies. 2025-05-16 15:37:55 +02:00			`maintainers = with lib.maintainers; [ grimmauld ];`
			`};`
			`} ./hook.sh`