home-assistant: fix packageOverrides ordering
As documented by lib.composeManyExtensions, overrides intended to be applied later should come last in the list. This commit switches the order to make sure that custom overrides are in fact evaluated after the default ones. Also, since the previous version was basically a reimplementation of composeManyExtensions anyway, switching to that makes it a bit cleaner.
This commit is contained in:
parent
c8585bf4a8
commit
b376ec113b
1 changed files with 1 additions and 2 deletions
|
@ -155,8 +155,7 @@ let
|
||||||
};
|
};
|
||||||
|
|
||||||
python = python3.override {
|
python = python3.override {
|
||||||
# Put packageOverrides at the start so they are applied after defaultOverrides
|
packageOverrides = lib.composeManyExtensions (defaultOverrides ++ [ packageOverrides ]);
|
||||||
packageOverrides = lib.foldr lib.composeExtensions (self: super: { }) ([ packageOverrides ] ++ defaultOverrides);
|
|
||||||
};
|
};
|
||||||
|
|
||||||
componentPackages = import ./component-packages.nix;
|
componentPackages = import ./component-packages.nix;
|
||||||
|
|
Loading…
Reference in a new issue