To add another data point, I also only use wine for gaming, so I was a bit confused about the error I got trying to update this package today, but I also was confused when initially installing the package months ago just to try out and having to remove wine-staging
to be able to do so.
@loathingkernel, as for suggestions, what do you think about about bringing back provides=wine
but keeping conflicts=wine
removed and keeping the installation in /opt? If I'm not mistaken, this would allow people to install other packages that require wine but not stop people from installing alternate versions of wine (e.g. the ones in the main repos) as well. For those of who don't want or need another version of wine, we could make a second package that symlinks things into the old locations (e.g. /usr/bin) and has conflicts=wine
to avoid issues, and this package could list it as an optional dependency (so that users installing this would be notified that they might want it as well). I guess this is sort of the same as the suggestion of having a separate wine-ge-custom-opt
but inverting which package retains the existing name, but this way lets you continue to maintain this package in the current state without having to create and maintain the second package yourself (since from the sentiments expressed here, it seems like there's enough of a desire that one of us would probably take the initiative).
Pinned Comments
loathingkernel commented on 2022-03-02 14:12 (UTC)
@Strykar Nope, see https://aur.archlinux.org/packages/wine-ge-custom#comment-831304
You can grab compiled packages from https://github.com/loathingKernel/PKGBUILDs/releases/tag/packages
loathingkernel commented on 2021-10-15 10:01 (UTC) (edited on 2021-10-15 10:04 (UTC) by loathingkernel)
@thaewrapt, I see, you might be correct. The prebuilt package is not a good candidate for packaging for a couple of reasons. First of all, it is built using Lutris's runtime, and as such inherits the same issues as Proton, namely it is at its best when running inside that runtime. Also, although I might be wrong here, I haven't found any mention of Lutris being able to use a system-wide installation directory in the same way Steam can. For these reasons, I believe that packaging those binaries is pointless and they should be managed by Lutris itself.