[virt-tools-list] [PATCH] wixl: use a versionized installation directory
Marc-André Lureau
mlureau at redhat.com
Mon Jan 26 10:21:41 UTC 2015
hi
----- Original Message -----
> On Mon, Jan 12, 2015 at 04:39:52PM +0100, Fabiano Fidêncio wrote:
> > From: Marc-André Lureau <marcandre.lureau at gmail.com>
> >
> > 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 ..?
mingw can't do much by itself. You need to create VERSIONINFO resource that is linked in the file (mingw provides windres, a .res.o compiler)
It will be very tedious to push fixes in all the binaries we use in remote-viewer.
More information about the virt-tools-list
mailing list