044534899b
The MSI file can contain different content with each change in build ID,
but the filename never changes. This creates confusion as to whether the
MSI is actually up to date or not. It requires the looking inside the
MSI to see the encoded version.
The RPM uses 2 components from the %release field as input for the build
ID value. Use these as two parts of the filename, separated from the
version with a "-" similar to how RPM version/release are separated.
IOW, an RPM
mingw32-virt-viewer-msi-9.0-1.fc33.noarch.rpm
will result in
virt-viewer-x64-9.0-1.0.msi
while
mingw32-virt-viewer-msi-9.0-1.fc33.1.noarch.rpm
will result in
virt-viewer-x64-9.0-1.1.msi
Essentially we've just stripped the %dist part (".fc33") out of
the release, and default the second component to "0" if omitted.
Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
Virt Viewer
Virt Viewer provides a graphical viewer for the guest OS display. At this time is supports guest OS using the VNC or SPICE protocols. Further protocols may be supported in the future as user demand dictates. The viewer can connect directly to both local and remotely hosted guest OS, optionally using SSL/TLS encryption.
Virt Viewer is the GTK3 application. Virt Viewer 3.0 was the last release that supported GTK2.
Virt Viewer uses the GTK-VNC (>= 0.4.0) widget to provide a display of the VNC protocol, which is available from
https://wiki.gnome.org/Projects/gtk-vnc
Virt Viewer uses the SPICE-GTK (>= 0.35) widget to provide a display of the SPICE protocol, which is available from:
https://www.spice-space.org/download.html
Use of either SPICE-GTK or GTK-VNC can be disabled at time
of configure, with --without-gtk-vnc or --without-spice-gtk
respectively.
Virt Viewer uses libvirt to lookup information about the guest OS display. This is available from
Bug reports / support questions should be submitted to
https://gitlab.com/virt-viewer/virt-viewer/-/issues
Code contributions should be submitted as merge requests to