[virt-tools-list] [virt-viewer PATCH V2] Add InstallScope="perMachine" to virt-viewer.wxs.in

[Sandy Stutsman]

It is a known bug that if an upgrade changes the InstallScope parameter:

http://stackoverflow.com/questions/678002/how-do-i-fix-the-upgrade-logic-of-a-wix-setup-after-changing-installscope-to-pe?rq=1

The best course of action seems to be to instruct users do do a manual install before reinstalling this new package.  This should be a one-shot action.


-S

----- Original Message -----
From: "Daniel P. Berrange" <berrange at redhat.com>
To: sstutsma at redhat.com
Cc: virt-tools-list at redhat.com
Sent: Tuesday, June 9, 2015 5:39:51 AM
Subject: Re: [virt-tools-list] [virt-viewer PATCH V2] Add InstallScope="perMachine" to virt-viewer.wxs.in

On Mon, Jun 08, 2015 at 03:21:02PM -0400, sstutsma at redhat.com wrote:
> From: Sandy Stutsman <sstutsma at redhat.com>
> 
> Addresses: https://bugzilla.redhat.com/show_bug.cgi?id=1146016
> Without this parameter the installer will place the start menu icon in the
> Admin users path rather than the 'AllUsers'.  Unprivileged users are unable
> to use the menu to start the remote-viewer.
> 
> N.B. Because previous installations mixed Users and PerMachine (AllUsers)
> paths, this installation will *NOT* properly upgrade them.  They must be
> manually uninstalled first.

In what way are upgrades broken ?  This is generally not something we
wish to break for obvious reasons.

Regards,
Daniel
-- 
|: http://berrange.com      -o-    http://www.flickr.com/photos/dberrange/ :|
|: http://libvirt.org              -o-             http://virt-manager.org :|
|: http://autobuild.org       -o-         http://search.cpan.org/~danberr/ :|
|: http://entangle-photo.org       -o-       http://live.gnome.org/gtk-vnc :|