Community Packages

Please read this before reporting a bug:
http://wiki.archlinux.org/index.php/Reporting_Bug_Guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#67141 - [winetricks] make wine a optional dependency

Attached to Project: Community Packages
Opened by No Name (Jaja) - Sunday, 28 June 2020, 17:49 GMT
Last edited by Felix Yan (felixonmars) - Sunday, 28 June 2020, 19:20 GMT
Task Type Feature Request
Category Packages: Multilib
Status Assigned   Reopened
Assigned To Felix Yan (felixonmars)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 0%
Votes 4
Private No

Details

Hi,

(co-)maintainer of "proton-ge-custom{,-stable,-legacy}-bin" here.
Since this version of proton includes protonfixes, winetricks i kind of needed to have all verbs play out as expected.
However, winetricks pulls in wine, which is unnecessary in this case.

Is it possible to change this? Nowadays the wine package is not the only software that will make use of winetricks.

Thanks!
This task depends upon

Comment by Felix Yan (felixonmars) - Sunday, 28 June 2020, 19:20 GMT
If your proton custom builds are actually providing alternatives to wine, should it provide wine instead?
Comment by No Name (Jaja) - Monday, 29 June 2020, 19:13 GMT
While this sounds logical, it is not reasonable imho.

There are plenty of custom wine and custom proton versions out there. Some of them, like the packages i maintain are monolithic and therefore could not easily "provide" wine. They simply fail on being a system wide meaningful/usable instance of wine. That being said, the mentioned packages provide "proton" (also as a command) system wide - but i think this is a different story.
Long story short: i don't think winetricks depends on wine - it just manipulates wine prefixes. And as i already wrote, these could be created from different origins like the plenty of fixed wine and/or proton versions that playonlinux and lutris can provide, if they are configured not to use the system installed wine. And of course there is protonfixes, which doesn't even refer to vanilla wine but proton.
Comment by G3ro (G3ro) - Friday, 07 August 2020, 15:13 GMT
I agree with jaja, there are multiple wine derivates etc. and in my case I use https://github.com/varmd/wine-wayland and the winetricks installation still wanted to install wine.

Everyone who installs winetricks will know that they need some kind of wine software.
Comment by Emil (xexaxo) - Monday, 21 December 2020, 19:41 GMT
Do correct me if I'm wrong - the proton packages (at least the ones I've seen) are a group of (patched) components:
- wine
- dxvk
- vkd3d
- others

As such, the proton packages should provide() and conflict() each of their components... yet none of them do so.
Please fix the AUR packages - proton and other wine-like ones. See the guidelines https://wiki.archlinux.org/index.php/PKGBUILD - for the mentioned sections.

Loading...