summaryrefslogtreecommitdiff
path: root/pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch
diff options
context:
space:
mode:
authoraszlig <aszlig@nix.build>2021-02-13 05:24:04 +0100
committeraszlig <aszlig@nix.build>2021-02-13 05:24:11 +0100
commit2d5a31a3ef2ce5b9b2aca610377e655924999000 (patch)
treebfad81989b0a17c31faa8a87b58302be3974d275 /pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch
parent29dcf53a5501e4144d00f001ad329dda287cbf9d (diff)
parent97718a3584377f9bce2f2b653c1b927c5d0f9286 (diff)
Merge pull request #112819 (mkIf in systemd units)
@thelegy writes: unitOption is only used inside of attrsOf wich is perfectly capable of handling the attrsets from mkIf, though the checkUnitConfig test forbids it. This commit weakens that restriction to allow the usage of mkIf inside of systemd.services.<name>.serviceConfig.<something> etc. While I personally don't like that we can't easily use pushDownProperties from the module system and need to rely on internals, we *already* use internals for the mkOverride case, so adding another case for mkIf doesn't add a hard-to-find indirection. I'm merging this, since this fixes a valid use case and it shouldn't make refactoring worse than before.
Diffstat (limited to 'pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch')
0 files changed, 0 insertions, 0 deletions