summaryrefslogtreecommitdiff
path: root/pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch
diff options
context:
space:
mode:
authorWolfgang Walther <walther@technowledgy.de>2025-05-29 16:32:19 +0200
committerWolfgang Walther <walther@technowledgy.de>2025-05-29 17:06:40 +0200
commitef1077013b863132e7429e946d221b4c810b5f53 (patch)
treeb6c735b39a0a221db51e42593670f0e15f9c7c97 /pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch
parent2f097cae61fd6062d863c7feba3fe3fa9f21eae0 (diff)
workflows/manual-nixpkgs: build nixpkgs manual on staging and stable branches
By using the pinned nixpkgs we have for CI, we can lift the restriction of building the nixpkgs manual only in PRs targeting master. At the same time, this uses the pinned nixpkgs for the doc/ folder's dev shell. This allows entering that shell while working on a staging-based branch and write documentation. Why should staging be un(der)documented, after all? Note: The package that is available in nixpkgs as pkgs.nixpkgs-manual will still be built with the current nixpkgs checkout, not the pinned version. This is the same that hydra builds.
Diffstat (limited to 'pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch')
0 files changed, 0 insertions, 0 deletions