On Thu, 27 Jan 2022 at 12:59, Vít Ondruch <vondruch(a)redhat.com> wrote:
Dne 27. 01. 22 v 12:18 Iñaki Ucar napsal(a):
> On Thu, 27 Jan 2022 at 12:09, Vít Ondruch <vondruch(a)redhat.com> wrote:
>>
>> Dne 27. 01. 22 v 11:19 Iñaki Ucar napsal(a):
>>> On Thu, 27 Jan 2022 at 10:58, Zbigniew Jędrzejewski-Szmek
>>> <zbyszek(a)in.waw.pl> wrote:
>>>>> I think this change should be reverted until a cleaner way can be
>>>>> found to implement it.
>>>> I'm all for making better, but please make concrete proposals.
>>> Here's a concrete proposal:
>>>
>>> - Copy %build_*flags to another private macro, let's say
%_build_*flags.
>>> - Add there the stuff that is not valid once the current build
>>> finishes (e.g., the flag that this change adds).
>>> - Use that in %set_build_flags and leave %build_*flags as it was.
>>>
>> That sounds similar to
>> "%extension_cflags/%extension_cxxflags/%extension_ldflags" Zbyszek
>> already mentioned elsewhere. Or I don't get the point.
>>
>> Here is concrete proposal for Ruby:
>>
>>
https://src.fedoraproject.org/rpms/ruby/pull-request/110
> There's a *big* difference: switching to %extension_*flags means that
> many packages have to be modified
But why? In Ruby, it should be enough to change Ruby itself and all the
other Ruby packages should be fine. Why is it different for R/OCAML?
In R, this could be enough for most packages too. But e.g. there are R
packages that are template builders for user programs, and probably
suffer from the same issue. The point is that we don't even know how
many packages are affected.
--
Iñaki Úcar