Nils Philippsen wrote:
> I beg to differ. When a tag in RPM can have multiple items (e.g.
> Provides, (Build)Requires), this …:
>
> Tag: item1 item2 item3
>
> … is consistently equivalent to this:
>
> Tag: item1
> Tag: item2
> Tag: item3
>
> To have ExclusiveArch behave differently would be surprising – nobody
> (😉) would read this and expect the effective list of arches the
> package would be built for to be empty:
>
> ExclusiveArch: x86_64
> ExclusiveArch: s390x
> ExclusiveArch: aarch64
+1. The current union behavior is reasonable, please do not change it
incompatibly (and inconsistenly with all other tags, as pointed out above).
Kevin Kofler
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
