summaryrefslogtreecommitdiff
path: root/pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch
diff options
context:
space:
mode:
authorEmily <vcs@emily.moe>2024-08-20 14:52:41 +0100
committerEmily <vcs@emily.moe>2024-08-22 01:54:09 +0100
commitafdee7e458b166e0d7252241444d9d1a7d52169c (patch)
tree16b87aa5b1b1e7bfbb44f67e729b08467ecbfcff /pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch
parent1a35d0ccb51c24f0c7d5ffffc802312b96a0319f (diff)
pict-rs_0_3: drop
This was broken by the Rust 1.80 upgrade, and is an old version that we’d have to patch to keep working. We have already done the 0.4 → 0.5 update without keeping around the old version or adding in any additional `stateVersion` logic in <https://github.com/NixOS/nixpkgs/pull/280221>. As a result, migration for 0.3 users is going to be a little awkward. I’ve done my best to provide comprehensive instructions for anyone who hasn’t already bumped to 0.4. It is probably a footgun to add `stateVersion` logic for any package that makes backwards‐incompatible schema changes and only supports migration from the immediately previous version. Users won’t get migrated by default and we have to either package and maintain an endlessly growing list of old versions or add complicated instructions like this. It’s not really practical for us to support a significantly better migration story than upstream does.
Diffstat (limited to 'pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch')
0 files changed, 0 insertions, 0 deletions