On Tue, Jun 10, 2014 at 11:49:39AM +0200, Marc-André Lureau wrote: > The main difference is that the NSIS is user installable, with destination > path selection. We are still using it for ActiveX auto-install. If it is > removed from upstream, we will have to keep maintaining it ourself > somewhere else and that can make maintenance/review/sharing a bit more > complicated. In general I'd prefer to have that upstream, it's simpler. But > I am ok if it is removed too. Hmm, is there any roadmap to converting the ActiveX usage to the MSI, or is that impossible ? If we need the NSIS installer for ActiveX long term then that's a good enough reason to keep it around. If we keep it around, it seems we should also publish this as part of the release process, otherwise its not really tested / exercised ? 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 :| _______________________________________________ virt-tools-list mailing list virt-tools-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/virt-tools-list
