On Tue, Sep 04, 2018 at 01:01:34PM +0200, Andrea Bolognani wrote: > Up until now, we've been considering MinGW builds as > part of the respective project, at least when it > comes to grouping them. This, however, does not quite > work for a number of reasons: > > * MinGW builds have their own workspace, separate > from the native one. It goes further than that: > even the 32-bit and 64-bit builds use a workspace > each, which goes to show that grouping all three > together is inaccurate; Well, I'd say that if someone cares enough about libvirt mingw builds, then they probably care about both ABI versions in which case they'd most probably prefer not having to specify for which x86 arch build they're interested in, therefore having both of these in the same project playbook, e.g. libvirt+mingw. Other than that, I'm completely in favour of splitting mingw into separate playbooks. Erik -- libvir-list mailing list libvir-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvir-list
