which release of Wine created or last updated this particular .wine/ tree?

Hi,

my HD contains a dozen .wine*/ directories created with various settings and releases of Wine, some a long time ago. A repeating question is:
With what release of Wine did I create this particular .wine/ tree ? Or rather: what release last updated this .wine/ tree?

It is not acceptable to run ~/src/most-current-wine/winecfg "about" on this .wine/ tree since an update that would change the bug footprint, causing the tested apps to work differently.

At the time of ~0.9.60, the answer was easy because tools/wine.inf was copied into .wine/drive_c/windows/inf/wine.inf and contained a release number.

Another possibility would be that I build a mini-DB of e.g. drive_c/windows/notepad's md5. Not very reliable, as notepad.exe need not change with every release.

Any other ideas?
    Jörg Höhle.

which release of Wine created or last updated this particular .wine/ tree?

[Ken Sharp]

Is anything dropped into the registry?

[e-mail] wrote:
> Hi,
>
> my HD contains a dozen .wine*/ directories created with various settings and releases of Wine, some a long time ago. A repeating question is:
> With what release of Wine did I create this particular .wine/ tree ? Or rather: what release last updated this .wine/ tree?
>
> It is not acceptable to run ~/src/most-current-wine/winecfg "about" on this .wine/ tree since an update that would change the bug footprint, causing the tested apps to work differently.
>
> At the time of ~0.9.60, the answer was easy because tools/wine.inf was copied into .wine/drive_c/windows/inf/wine.inf and contained a release number.
>
> Another possibility would be that I build a mini-DB of e.g. drive_c/windows/notepad's md5. Not very reliable, as notepad.exe need not change with every release.
>
> Any other ideas?
>    Jörg Höhle.

Ken Sharp wrote:
> Is anything dropped into the registry?

No. One of my .wine/ trees uses Git and I can tell that for some releases, there
are no changes in the registry except for the time stamp of some keys (...\Fonts
among them).
It would not be nice to add some registry just to track the version.

One idea I had was to use the 0-length .wine/.update-timestamp and write a
version string into it. Of course that would not help for past releases.

BTW, putting .wine under version control is a great way to assess
what an application installs.

Regards,
    Jörg Höhle

which release of Wine created or last updated this particular .wine/ tree?

[James McKenzie]

[e-mail] wrote:
> Ken Sharp wrote:
> > Is anything dropped into the registry?
>
> No. One of my .wine/ trees uses Git and I can tell that for some releases, there
> are no changes in the registry except for the time stamp of some keys (...\Fonts
> among them).
> It would not be nice to add some registry just to track the version.
>
> One idea I had was to use the 0-length .wine/.update-timestamp and write a
> version string into it. Of course that would not help for past releases.
>
> BTW, putting .wine under version control is a great way to assess
> what an application installs.

+1, from a CM kind of guy.

James McKenzie