On 2/4/26 8:32 PM, Morten Linderud wrote:
Please stop dropping random tooling into our repos with 0 consensus and
encourage it's use. This is not the first time you've have done this.
I'm not dealing with the consequences here.
This is not helping anyone and just giving me a bunch of future problems.
I appreciate your effort on gcc (I really do!) but please don't problem-squat
and put down other people's work if you don't have an alternative solution ready
(e.g. rolling out /etc/makepkg.conf.d/go.conf in the imminent future).
There is similar tooling in the openSUSE project that we also carry in our
repository since exactly 1 year:
https://archlinux.org/packages/extra/any/reproducible-faketools/
We have a similar wrapper for meson at /usr/bin/arch-meson, they are both very
explicitly opt-in, and I'm absolutely happy to drop mine once it has been
obsoleted, but not before.
In the past 2 years I have been the only person pushing this topic[1] (again, I
do acknowledge and appreciate the work you do/did on gcc+go around the same
time, but it only solves the LTO problem, not the build flag situation).
[1]:
https://lists.archlinux.org/archives/list/[email protected]/thread/Z7GGEN7YO65S343G5JBW3AIIWDJQNDHZ/
cheers,
kpcyrd
