On Fri, Sep 2, 2022 at 3:45 AM Daniel P. Berrangé <berrange@redhat.com> wrote:
On Thu, Sep 01, 2022 at 04:25:28PM -0500, Richard Shaw wrote:
> On Thu, Sep 1, 2022 at 12:38 PM Sandro Mani <manisandro@gmail.com> wrote:
>
> >
> > On 01.09.22 17:18, Richard Shaw wrote:
> > > I'd like to unify fltk but there are a couple of things I'm still
> > > unclear about...
> > >
> > > 1. If I build the x86_64 package locally via fedpkg or mock, will it
> > > build both the linux and mingw artifacts by default?
> > Unless you have any specific %ifarch etc, yes.
> > > 2. Since mingw packages are considered "noarch" in infrastructure, I
> > > assume there's some magic to prevent arches other than x86_64 from
> > > attempting to build the mingw packages?
> > Not really, but if builders on separate arches produce different
> > artifacts for the noarch packages, the build will fail with a
> > corresponding message like "package XXX built differently on arches YYY"
> >
>
> Let me rephrase, is the mingw package going to be built on ALL arches with
> the expectation that they are the same (like -data packages)? If so, that
> seems like a huge waste of resources.

If looking at a single package in isolation it may look wasteful, but from
the POV of the distro as a whole packages with potential mingw sub-RPMs
are a small subset of what goes through koji every day.

Perhaps, but the engineer in me finds this very distasteful :)

It would probably be too much work but it would be useful to have a pseudo-arch "mingw" which would just build on the first available "noarch" builder. 

Thanks,
Richard