This reverts commit 0ee2449821.
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.
This mostly reverts commit 63a365d8ff.
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.
This reverts commit 801b31bb36.
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.
This reverts commit d9344e9f67.
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.
I was added based on my maintainership in grafana-agent.
And now that grafana-agent was dropped from nixpkgs, I had a deeper look
at grafana-alloy once again and I am still not happy with it.
So I decided to migrate to something else than grafana-alloy and am
dropping my maintainership accordingly.
