On Thu, Sep 01, 2022 at 04:57:52PM -0500, Michael Cronenworth wrote:
On 9/1/22 4:25 PM, Richard Shaw wrote:
> 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.
The MinGW packages would build on all arches. I believe the original
designation of 'noarch' is due to the cross-compile aspect as you can build
these on any arch and that end users would only use them for development and
not runtime. That has changed recently now that Wine builds most of itself
as Windows PE binaries and depends on .dll files from mingw32/64 packages.
The distinction 'development' vs 'runtime' is rather ill-defined, since
development includes running tests which is "runtime" usage. Even before
Wine was using the DLLs itself, apps could run their own tests inside
Wine, or inside a real Windows virtual machine, at their choice. It is
still reasonable to have the mingw packages noarch, as for example, people
could be using a aarch64 host, doing windows cross-builds for compile
only testing and so need the mingw packages installed.
With regards,
Daniel
--
|:
https://berrange.com -o-
https://www.flickr.com/photos/dberrange :|
|:
https://libvirt.org -o-
https://fstop138.berrange.com :|
|:
https://entangle-photo.org -o-
https://www.instagram.com/dberrange :|