diff options
| author | polykernel <81340136+polykernel@users.noreply.github.com> | 2021-10-31 22:14:45 -0400 |
|---|---|---|
| committer | polykernel <81340136+polykernel@users.noreply.github.com> | 2022-08-28 19:17:14 -0400 |
| commit | a983d4e779dcd0fa05e5d227233cdd29702e7e89 (patch) | |
| tree | cf331a554fe8288400f9f2c272594fcae52dec43 /pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch | |
| parent | 36f77596b1fc34b3b556cf2f17ee1fe05b20ff51 (diff) | |
fuzzel: refactor configure options
The current configure options exposed emulates the `choices` type of the
SVG and PNG backends from upstream meson_options with a freeform string,
however this is error prone and require accompanying validation which
unnecessarily complicates the derivation. Two alternatives were considered:
1. Splits the possible choices into separate options nad perform assertions to
ensure only one is selected.
2. Expose a set of sane default configure options, and structure the derivation
around this subset. Users who wish to customize the choice used can do so
using `override` or `overrideAttrs`.
Option 1 is not sustainable for large amounts of options which require large
amount of assertions just for ensuring uniqueness of selection, and adds
complexity to the configure phase. Option 2 minimally impairs the customizablity
of the derivation and was chosen in part to address option checking[1].
[1] - https://github.com/NixOS/nixpkgs/pull/141836#discussion_r739910095
Diffstat (limited to 'pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch')
0 files changed, 0 insertions, 0 deletions
