Currently, `system.patches` doesn't work because it will attempt to first detect if the patch has already been applied by checking if it can be applied in reverse. However, when that happens, `patch` detects that the supplied patch is incorrectly reversed and attempts to ask the user if they want to "Ignore -R": ``` Unreversed (or previously applied) patch detected! Ignore -R? [y] ``` Because the output is piped to `/dev/null` the user will basically see nothing and `darwin-rebuild switch` will hang until the user presses "Enter" (possibly to check if the terminal is frozen). At which point, patch will ignore the --reverse and exit successfully, preventing the patch from being applied at all. This change fixes that bug by using `--force` which tells patch that we know what we're doing and prevents it from prompting the user if they want to ignore `--reverse`. |
||
|---|---|---|
| .. | ||
| defaults | ||
| activation-scripts.nix | ||
| applications.nix | ||
| checks.nix | ||
| default.nix | ||
| defaults-write.nix | ||
| etc.nix | ||
| flake-overrides.nix | ||
| keyboard.nix | ||
| launchd.nix | ||
| patches.nix | ||
| shells.nix | ||
| version.nix | ||