[virt-tools-list] [PATCH virtio-win-pkg-scripts v3 0/2] helpers to standardize driver directory layout
cfergeau at redhat.com
Mon Feb 29 13:19:15 UTC 2016
On Wed, Feb 17, 2016 at 06:11:31PM -0500, Cole Robinson wrote:
> > 3) current virtio-win package includes several loosely related packages:
> > virtio drivers, qxl, qga; we add our own, too. They have independent
> > release cycles and build procedures (e.g. qga builds nicely with
> > mingw on Linux and can be turned into a normal rpm suitable for
> > shipping in e.g. Fedora)
> Certainly for the public virtio-win distribution there's no good reason to be
> dependent on internal RH builds for qemu-guest-agent. It only works like that
> because I haven't gotten fixing it.
> There's a question then of where we get our qemu-guest-agent build. I don't
> know if having a mingw-qemu-guest-agent RPM in fedora would be acceptable,
> shipping a windows binary like that. It could be a separate RPM that is
> distributed in the virtio-win.repo but it'll take a bit of scripting to set up.
I think at the time mingw was added to fedora, the outcome was that
.dlls were good to be built/shipped in fedora repos, but that end-user
.exe files would not belong there (at least this is my
understanding/what I was told). Dunno if that is wrong/if this has
changed. This is why mingw-virt-viewer or mingw-spice-vdagent are not in
fedora repos for example.
A copr repository, or something on the Open Build Service would most
likely work for building/distribution though.
> But while it seems feasible for the public distribution, it's less so for
> RHEL. RHEL doesn't have mingw and likely never will.
mingw can be used for building as this is how virt-viewer for Windows is
built for RHEV. The mingw-* packages are probably not exposed/shipped to
RHEL users though.
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 819 bytes
Desc: not available
More information about the virt-tools-list