On Wed, Oct 26, 2022 at 10:23:40AM +0200, Florian Weimer wrote:
* Zbigniew Jędrzejewski-Szmek:
> On Tue, Oct 25, 2022 at 10:05:52AM -0400, Ben Cotton wrote:
...snip...
>> == How To Test ==
>
> As discussed by others, this needs to explain how to opt-in for early
> testing, and also how to opt-out in packages, how to opt-out as a user
> (if the default touches users), etc.
The challenge with that is that I've been told not to do this work in
Fedora proper by release engineering, and a request for a long-living
side tag with a suitable compiler has not been approved:
Long-term side tag for toolchain experiment
<
https://pagure.io/releng/issue/10392>
Sorry that got dropped...
The thread about it I suggested copr, some other folks thought that
might work, and I don't recall ever hearing if that would work for you
or not. So, seems communication broke down here somewhere.
I suppose it's too late now for this to matter aside from us trying to
not have it happen again? In the future, if a releng issue gets stuck,
please do drop by the releng and infra standups (mon/tue/wed/thu) at
18UTC in #fedora-meeting-3 /
meeting-3:fedoraproject.org and bring up
the issue.
More recently, I was explicitly told not to keep the compiler changes
on
a branch in Fedora dist-git.
It is not really possible to get realistic testing through compiler flag
injection because crufty old code that is problematic for these changes
often does not inject flags properly. Certain likely changes cannot be
modeled through -Werror= options (but can be patched into GCC). Some
build systems explicitly filter out -Werror= options during the
configure stage (generally a good idea, but not helpful here).
So I'm a bit at a loss what to do here. Maybe releng can reconsider
their approach.
So, can you say that copr definitely will not work for this?
If it will, great, use that. If it won't, we can make you a side tag, I
don't really have any objection to it other than it seems like copr was
better designed for this sort of work...
kevin