Am 12.11.19 um 14:49 schrieb Fabio Valentini:
On Tue, Nov 12, 2019 at 1:44 PM Felix Schwarz wrote:
Am 12.11.19 um 13:37 schrieb Fabio Valentini:
There's a specific section about this issue in the Packaging Guidelines:
https://docs.fedoraproject.org/en-US/packaging-guidelines/#_noarch_with_unported_dependencies
So, in your case, I think you'd have to use something like this:
BuildArch: noarch
ExclusiveArch: x86_64 %{ix86} aarch64 ppc64le noarch
I read this paragraph but it also says:
"You can limit both the architectures used to build a noarch package, and the
repositories to which the built noarch package will be added, by using either
the ExcludeArch: or ExclusiveArch: tags:"
English is not my first language but I understood this as if I could use also
"ExcludeArch" (which I did as it matches Thunderbird better).
It's not my first language either ;)
I used ExclusiveArch in my example though, because you don't want to
*exclude* noarch, but *include* it.
I'm sorry but I still don't get it.
Currently I have these lines in thunderbird-enigmail's .spec file:
,---------------------------------
BuildArch: noarch
# Thunderbird is not available on all supported platforms
ExcludeArch: armv7hl
ExcludeArch: s390x
`---------------------------------
To me that means: Package can be built with "noarch" but should not be
available on "armv7hl"/"s390x".
1) How do I exclude "noarch" here?
2) How is "ExclusiveArch" better?
Do I really have to list all "other" Fedora architectures (as
"ExclusiveArch" requires)?
Especially given the text in the packaging guidelines I'd expect that both
approaches should work.
Felix
_______________________________________________
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
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@lists.fedoraproject.org
