summaryrefslogtreecommitdiff
path: root/pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch
diff options
context:
space:
mode:
authorsternenseemann <sternenseemann@systemli.org>2021-12-16 09:13:30 -0400
committersternenseemann <sternenseemann@systemli.org>2023-01-15 17:35:42 +0100
commit727491cd957632ae9dc0449f3600999b40a8a61a (patch)
tree350f7b2428790fd5446b9a0e5eab04bacf7cd8b0 /pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch
parent02cbec616aa7b7cafe3b76a39031c0c74c07106a (diff)
ghc.withPackages: install documentation to -with-packages output
* Will make it so that GHC.Paths's docdir NIX_GHC_DOCDIR points to an actual directory. * Documentation of all packages in the environment is available in `$out/share/doc`. This has previously been attempted in #76842 and reverted in #77442, since documentation can collide when the libraries wouldn't (thanks to the hash in the lib filename). `symlinkJoin` allows collision, so this solution should be akin to #77523 (minus `buildEnv`, one step at a time). `installDocumentation = false` restores the old behavior. Collision in the documentation only happen if the dependency closure of the given packages has more than one different derivation for the same library of the very same version. I'm personally inclined not to claim that our infrastructure does anything sensible in this case. Additionally, the documentation is likely largely the same in such cases (unless it is heavily patched). Resolves #150666. Resolves #76837. Closes #150968. Closes #77523.
Diffstat (limited to 'pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch')
0 files changed, 0 insertions, 0 deletions