On Mon, Jan 12, 2015 at 04:39:52PM +0100, Fabiano Fidêncio wrote: > From: Marc-André Lureau <marcandre.lureau@xxxxxxxxx> > > It turned out that not only the current MSI broke the "component rule", > but also that our files are not versionized correctly. Windows Installer > applies some file versioning rules before replacing a file > http://msdn.microsoft.com/en-us/library/aa368599%28v=vs.85%29.aspx > > Since msitools doesn't extract version from files and populate the Version > field of the File table, it "usually" keep the current file installed. > > It's practically impossible to rely on version information from > files (from a quick look, only 5% of the files are versionized and even > less correctly, libgcrypt seems to do non-monotonic buildid for example) Is there something mingw can do to version files correctly? I'd never even heard of this feature of Windows before. Where is the version stored? In the file? In an NTFS ADS ..? Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com virt-p2v converts physical machines to virtual machines. Boot with a live CD or over the network (PXE) and turn machines into KVM guests. http://libguestfs.org/virt-v2v _______________________________________________ virt-tools-list mailing list virt-tools-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/virt-tools-list
