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:
Yannik Rödel 2022-07-19 13:25:52 +02:00 committed by GitHub
parent c8585bf4a8
commit b376ec113b
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23

View file

@ -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;