On Mon, Nov 14, 2016 at 3:37 PM, Pavel Raiskup <praiskup(a)redhat.com> wrote:
On Wednesday, September 21, 2016 12:55:48 PM CET Jason L Tibbitts III
> First off, the guidelines have:
> I've been assuming that you're talking about the BuildRequires: case.
> If you're just talking about the case where you can build it anywhere
> because you're just copying files around, but it just won't install,
> then you can try doing the noarch/ExclusiveArch: trick. To be fair, I
> have no idea if it still works; I recall that some people really didn't
> like it. Of course if it doesn't work then I'll remove that bit from
> the guidelines. I've sent out a couple of questions to folks who should
> know better than I.
To close this for fedora-devel too, the ExclusiveArch trick probably
doesn't work at least in my case  because:
- I set ExclusiveArch for set of sub-packages only
Exclusive/Exclude arch only works for the whole package, not for sub
packages, it's global to the extire spec. If you want to exclude
package based on arch (why?) you need to do %ifarch conditionals for
the sub package components.
> - I've added 'noarch' into ExclusiveArch, because of the bug 1298668
> Orion mentioned.
> Can this be somehow reflected in guidelines ? I don't really know how,
> but at least in case of vim-syntastic -> I'm against adding ExclusiveArch
> into vim-syntastic (that means if single _sub_package doesn't work on say
> aarch64, every other sub-package will be excluded from aarch64).
>  https://pagure.io/pungi-fedora/issue/87
>  https://fedoraproject.org/wiki/Packaging:Guidelines
> devel mailing list -- devel(a)lists.fedoraproject.org
> To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org