Add support for Debian/RHEL Alternatives + Gentoo virtual/wine

[brezerk]

as per @tehnick comment https://github.com/brezerk/q4wine/issues/139#issuecomment-425414254:

Not related to bug report, but you may be interested... In Debian and distros based on it WINE in currently packaged by this way:

$ ls -alp /usr/bin/wine*
lrwxrwxrwx 1 root root     22 авг 29  2016 /usr/bin/wine -> /etc/alternatives/wine
lrwxrwxrwx 1 root root     24 авг 29  2016 /usr/bin/wine64 -> /etc/alternatives/wine64
lrwxrwxrwx 1 root root     18 июл 24 03:48 /usr/bin/wine64-stable -> ../lib/wine/wine64
lrwxrwxrwx 1 root root     26 авг 29  2016 /usr/bin/wineboot -> /etc/alternatives/wineboot
lrwxrwxrwx 1 root root     25 июл 24 03:48 /usr/bin/wineboot-stable -> ../lib/wine/wineapploader
lrwxrwxrwx 1 root root     25 авг 29  2016 /usr/bin/winecfg -> /etc/alternatives/winecfg
lrwxrwxrwx 1 root root     25 июл 24 03:48 /usr/bin/winecfg-stable -> ../lib/wine/wineapploader
lrwxrwxrwx 1 root root     29 авг 29  2016 /usr/bin/wineconsole -> /etc/alternatives/wineconsole
lrwxrwxrwx 1 root root     25 июл 24 03:48 /usr/bin/wineconsole-stable -> ../lib/wine/wineapploader
lrwxrwxrwx 1 root root     25 авг 29  2016 /usr/bin/winedbg -> /etc/alternatives/winedbg
lrwxrwxrwx 1 root root     25 июл 24 03:48 /usr/bin/winedbg-stable -> ../lib/wine/wineapploader
lrwxrwxrwx 1 root root     26 авг 29  2016 /usr/bin/winefile -> /etc/alternatives/winefile
lrwxrwxrwx 1 root root     25 июл 24 03:48 /usr/bin/winefile-stable -> ../lib/wine/wineapploader
lrwxrwxrwx 1 root root     26 авг 29  2016 /usr/bin/winepath -> /etc/alternatives/winepath
lrwxrwxrwx 1 root root     25 июл 24 03:48 /usr/bin/winepath-stable -> ../lib/wine/wineapploader
lrwxrwxrwx 1 root root     28 авг 29  2016 /usr/bin/wineserver -> /etc/alternatives/wineserver
lrwxrwxrwx 1 root root     22 июл 24 03:48 /usr/bin/wineserver-stable -> ../lib/wine/wineserver
-rwxr-xr-x 1 root root   1019 июл 24 03:48 /usr/bin/wine-stable
-rwxr-xr-x 1 root root 723026 июн  3 17:55 /usr/bin/winetricks

$ ls -alp /usr/lib/wine/
итого 1152
drwxr-xr-x   2 root root   4096 авг  8 11:44 ./
drwxr-xr-x 151 root root  20480 сен 25 12:54 ../
-rwxr-xr-x   1 root root  13692 июл 24 03:48 wine
-rwxr-xr-x   1 root root  14352 июл 24 03:48 wine64
-rwxr-xr-x   1 root root  17192 июл 24 03:48 wine64-preloader
-rwxr-xr-x   1 root root    115 июл 24 03:48 wineapploader
-rwxr-xr-x   1 root root  16988 июл 24 03:48 wine-preloader
-rwxr-xr-x   1 root root    351 июл 24 03:48 wineserver
-rwxr-xr-x   1 root root 517788 июл 24 03:48 wineserver32
-rwxr-xr-x   1 root root 551464 июл 24 03:48 wineserver64

also, Gentoo provides virtual/wine a kind of Alternatives, might be interesting too:

[ himera ] brezerk@pts/0:24  ~/Develop/q4wine $
 01/02/19 01:10:06 EET > ls /usr/share/ | grep wine
drwxr-xr-x   5 root root  4096 Nov  5 20:42 wine-staging-3.19
drwxr-xr-x   5 root root  4096 Dec  1 00:19 wine-staging-3.21

[Eonfge]

This issue would become unimportant if a functional Flatpak becomes available. It will then be q4wine's task to directly bundle Wine Stable 32/64bit and Wine Testing 32/64 bit.

[tehnick]

@Eonfge Most of users use packages from official repositories.

Flatpak, snap, AppImage, etc. may be useful for some users of course, but they are not a replacement for classical packages.

[Nokia808]

@tehnick Dear flatpak is better regarding security. WineHQ can run viruses & spywares. Regarding system packages (.deb/.rpm) currently I'm using this approach to avoid WineHQ evils: https://forums.fedoraforum.org/showthread.php?313858-Risk-Free-WineHQ-Installation-amp-Usage

While all we have to do with flatpak from FlatHub is:

1. create new user account: sudo useradd -m -d /windows/data -s /bin/bash wineuser sudo passwd wineuser rebbot
2. disable wineuser from ability to use sudo & su: a- sudo already disabled by default on Fedora for any newly created user account which by default out of wheel group b- disable any newly added user account from utilizing su by: sudo vi /etc/pam.d/su then uncomment the following line: #auth required pam_wheel.so use_uid then save & exit by :wq reboot
3. make "wineuser" not able to use polkit. On Cinnamon DE by: sudo setfacl -m u:wineuser:--- /usr/libexec/polkit-gnome-authentication-agent-1
4. login to "wineuser" account, then install q4wine flatpak from FlatHub as a user using "--user" flag: flatpak install --user flathub

The safety is the chief credential of flatpak package ...... System packages or AppImage are never secure by default.

[tehnick]

And now compare the amount of regular users who follow instructions described by you with amount of users who just do sudo apt install q4wine and begin using WINE without worrying about malware...

[Nokia808]

@tehnick Dear friend ! The 1st listen that I learned from Linux is that: "NOT every things done by regular users are correct". Taking your idea (the thing done by MOST of regular users", then we should shift from Linux to Windows as MOST of regular users use Windows, isn't it ?!!

After 11 years from using Windows, I discover Linux & now after 4 years Linux using, I feel my self discovered for 11 years by Windows ! Viruses, spywares, & even if not injured by them, your Windows files will damage just from continuity in use ! So, is what currently done by MOST of regular users is the correct thing ??

We should not encourage wrong ways & we should keep on ideal path (safety + security + usability + durability + no viruses + no spaywares)

[tehnick]

The 1st listen that I learned from Linux is that: "NOT every things done by regular users are correct".

And so what? GNU/Linux systems are extremely flexible in setup and allow users do almost everything what they want.

If you wish to use Flatpak with all its features it is only your choice. Most of users use system package manager and will use it in foreseeable feature. And they should not be limited anyhow because someone in the Internet believes that everyone should use Flatpak because this is more secure and the only one true way (in his(her) thoughts).

Taking your idea (the thing done by MOST of regular users", then we should shift from Linux to Windows as MOST of regular users use Windows, isn't it ?!!

You are making false conclusions based on false assumptions using incorrect logic.

After 11 years from using Windows, I discover Linux & now after 4 years Linux using, I feel my self discovered for 11 years by Windows ! Viruses, spywares, & even if not injured by them, your Windows files will damage just from continuity in use !

I'm happy for you. It looks that your path to GNU/Linux from MS Windows was long and thorny...

My experience is a bit different: I use GNU/Linux as a primary OS since 2006 for all my tasks (study, relax, work, hobby, etc.). Due to my job (software development) and one of hobbies (FOSS development) I have additional experience of using of MS Windows, macOS, FreeBSD and Haiku from both sides: as programmer and as user. So I have more than enough information about their strong and weak sides...

And as far as I see the main reason of different troubles is not in operating system but in users who are vulnerable to methods of social engineering.

BTW, some time ago I even had a small collection of malware (have in mind that viruses and spyware are just a small part of different types of malware) and I have tried to launch it with different versions of WINE (not in my main system, if you worry). To my sadness almost all of these programs had being falling with different errors...

So, is what currently done by MOST of regular users is the correct thing ??

I do not care about users of some exterior software which is off-topic here. But I do care about q4wine users in common and Debian and Ubuntu users in particular.

We should not encourage wrong ways & we should keep on ideal path (safety + security + usability + durability + no viruses + no spaywares)

And again: this is only your opinion about "wrong" and "correct" ways here. Some people may agree with you, some people have another opinion. And it is not erroneous, it is just another...

I may bring my particular cases of q4wine usage.

At work I use 32-bit and 64-bit versions of WINE only for testing some functions of software developed by me and my colleagues when I do not need to launch whole MS Windows in VirtualBox. At home I use WINE only for launching FOSS programs compiled by myself. My wife, parents and little brother do not launch pirate software or software from untrusted sources as well.

And why should we use Flatpak, Snap, AppImage+firejail? There are no pros for this at all, but there are obvious cons like wasting of disk space and sandboxs limitations...

In any case this discussion is completely useless here. Probably all comments unrelated to issue topic should be removed once discussion is finished.