Running more than one fully independent and isolated wine environments on the same computer.

[hongyi-zhao]

Hi,

I've two Window's applications which need different wine versions and I want to run then at the same time. In this case, I must run two fully independent and isolated wine environments on the same computer for each of them. Any hints for the trick to achieve this aim?

Regards,
HY

[dimesio]

You didn't mention what distro you're using, but if it's Fedora, Debian, or Ubuntu, the WineHQ packages are designed to allow users to install all three branches side-by-side, so you could install the stable, development, and staging packages at the same time. However, you cannot install two different packaged versions of the same branch at the same time. If that's what you need, the easiest way to accomplish that is to build the versions of Wine you need yourself and not install them--just run them from the build directory. You should also create separate wineprefixes for your apps.
https://wiki.winehq.org/FAQ#Can_I_insta ... _system.3F
https://wiki.winehq.org/FAQ#Can_I_store ... 2F.wine.3F

[hongyi-zhao]

I use Ubuntu 20.04 and wine git master version compiled by myself.

The current issue for my case is as follows: I use the self-cimpiled wine to run an application, at the same time I also installed the other version of wine, customized by deepin distro, from here: http://mirrors.aliyun.com/deepin/pool/n ... eepin-wine for running some other applications.

I find the following problem for my case when using the above two different wine to start applications at the same time: The first started wine's wineserver will be used the subsequent started wine which will cause the failure for its running.

[spoon0042]

Also note that if, again, you're using the WineHQ built packages you can install a certain version then copy the whole wine tree somewhere. If the thought of compiling scares you off.

e: I know it's not supported here and all but if you have more than a couple of things needing different wine versions this may be a use case for PlayOnLinux or something similar. In the other direction if you have a program that works in an older version of wine and doesn't work on current that's a bug that could be worth reporting.

[dimesio]

I find the following problem for my case when using the above two different wine to start applications at the same time: The first started wine's wineserver will be used the subsequent started wine which will cause the failure for its running.

Did you create separate wineprefixes for the apps and did you specify the full path to the specific wine version you wanted to use for each? You need to do both.

[hongyi-zhao]

[/quote]
Did you create separate wineprefixes for the apps and did you specify the full path to the specific wine version you wanted to use for each? You need to do both.
[/quote]

I use different WINEPREFIX environment variable for each of them like the following:

Code: Select all

$ env WINEPREFIX=/path/to/wine-app wine ...
$ env WINEPREFIX=/path/to/deepin-wine-app deepin-wine ...

As you can see, the binary names of these wine versions are different and can be picked up correctly without using full-path. See following for more info:

Code: Select all

werner@X10DAi-01:~$ which deepin-wine
/usr/bin/deepin-wine
werner@X10DAi-01:~$ which wine
/usr/local/bin/wine

[hongyi-zhao]

Any more hints on this problem?

[jury]

Have you tried PlayOnLinux suggested before by spoon0042. There is no other so simple and straightforward way for using countless wine versions on one machine.