diff options
| author | polykernel <81340136+polykernel@users.noreply.github.com> | 2022-02-12 13:47:19 -0500 |
|---|---|---|
| committer | polykernel <81340136+polykernel@users.noreply.github.com> | 2022-02-12 17:15:31 -0500 |
| commit | 34636a8525322da7945cc01c70dfb08366c5a128 (patch) | |
| tree | bda1fb655019c8fdee56259432ed25aac9e93178 /pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch | |
| parent | e8d0ffa08ca1ee49733bbb24848a10e1d722ea02 (diff) | |
nixos/nix-daemon: Fix merging order for substituters option
The `substituters` option in `nix.settings` uses the order
of the substituters listed to define priority. Prior to https://github.com/NixOS/nixpkgs/pull/139075,
the corresponding option `binaryCaches` is declared in the `nix` namespace,
which is guaranteed to be merged last. However, the order of merging isn't
guaranteed in submodules. This cause definitions to be appended to the default
value instead of prepended, breaking backwards compatibility as reported in https://github.com/NixOS/nixpkgs/issues/158356.
The way this is addressed in the module system is with order priorities via
`mkOrder` and sorting definitions before merging. This PR restores the previous
behavior by setting a higher priority to the substituters option defined internally,
thus all definitions with default priority will be merged before it. This was chosen because
the `mkRenamedOption` function does not preserve order priority so users using legacy options do not have
precise control on placement.
This change should suffice for simple configuration, but further revision to the module system
is needed for to make various `mk*` functions aware of order priorities.
Diffstat (limited to 'pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch')
0 files changed, 0 insertions, 0 deletions