mirror of
https://github.com/nix-community/home-manager.git
synced 2025-03-10 10:47:02 +00:00
When `cfg.package` is already wrapped, and wrapped without the `ExtensionSettings` key set, this would always add that key, even if its value was blank. This would result in `cfg.finalPackage` being a functionally-identical, but differently-input-addressed package. This is generally undesirable as it may result in multiple derivations being built, and also if the value of `cfg.package` is expected to be unchanged by the user (e.g. because they want it to be consistent between NixOS and HM configuration). Add a test to ensure this does not regress in the default case. Only test on newish stateVersion since the logic for `isWrapped` differs on older versions.
17 lines
838 B
Nix
17 lines
838 B
Nix
name:
|
|
builtins.mapAttrs (test: module: import module [ "programs" name ]) {
|
|
"${name}-deprecated-native-messenger" = ./deprecated-native-messenger.nix;
|
|
"${name}-final-package" = ./final-package.nix;
|
|
"${name}-policies" = ./policies.nix;
|
|
"${name}-profiles-bookmarks" = ./profiles/bookmarks;
|
|
"${name}-profiles-containers" = ./profiles/containers;
|
|
"${name}-profiles-containers-duplicate-ids" =
|
|
./profiles/containers/duplicate-ids.nix;
|
|
"${name}-profiles-containers-id-out-of-range" =
|
|
./profiles/containers/id-out-of-range.nix;
|
|
"${name}-profiles-duplicate-ids" = ./profiles/duplicate-ids.nix;
|
|
"${name}-profiles-search" = ./profiles/search;
|
|
"${name}-profiles-settings" = ./profiles/settings;
|
|
"${name}-state-version-19_09" = ./state-version-19_09.nix;
|
|
"${name}-profiles-shared-path" = ./profiles/shared-path.nix;
|
|
}
|