Closed #2319 as completed.
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/2319#event-10766742033
You are receiving this because you are subscribed to this thread.
Message ID:
___
Rpm-maint
So I think going back to the old behaviour is just not worth the trouble - even
if it may be easy to do code wise. So all that's left is cleaning up the code a
little bit. Not keeping a ticket open for stuff like that - otherwise we had
tickets for each line of RPM code...
--
Reply to this
I also don't have too strong of an opinion on that. Only the comment that most
build systems may be pretty surprised if suddenly packages from more than one
build arch show up. May be we should keep things as they are and just clean up
the code.
--
Reply to this email directly or view it on
I really don't remember the behavior from those days, no strong opinion here.
Other than agreeing on "it seems pretty broken in many places" that is.
As for optflags - yes, and BuildArch should arguably also (re)load platform
macros while at it.
--
Reply to this email directly or view it on
The documentation is somewhat lacking, but it seems to me that once upon a time
specifying multiple elements in BuildArch resulted in multiple builds being
done (if the buildarch is deemed compatible).
I think this was broken in 2001 with commit
c3835f5ca0e3ea856213a22367233e148ea26550, which
