diff options
| author | Alyssa Ross <hi@alyssa.is> | 2025-03-31 17:22:10 +0200 |
|---|---|---|
| committer | Alyssa Ross <hi@alyssa.is> | 2025-04-08 17:58:51 +0200 |
| commit | 588d8570a155ce50e48f24019cbcbe5f6156db30 (patch) | |
| tree | ae4e3485772faddbe3852439cd67f6ca270869a7 /pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch | |
| parent | 9cde6b86e9b5e1094695862bad811a251f7a94d1 (diff) | |
Revert "cosmic-launcher: use mold linker"
This mostly reverts commit 63a365d8ffd47ffe7bbd0e577e3fecb51130efed.
I've left the deletion of the postPatch from the original commit stand
— it seems to have been included in the original commit by mistake
instead of being a separate commit, as it has nothing to do with mold.
In Nixpkgs, we consider the linker a property of the platform.
Individual packages should not be using toolchains other than the ones
that are part of the platform without a strong justification. In this
case, the only justification appears to have been that upstream uses
this linker. Just like we don't force every package whose upstream
happens to use Clang in their own builds to build with Clang in
Nixpkgs rather than the platform compiler, upstream's choice alone
isn't grounds for overriding the platform linker here.
Diffstat (limited to 'pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch')
0 files changed, 0 insertions, 0 deletions
