@endlesik It is not the package but the sources, wine-ge-custom
has been rebased on Valve's wine fork instead of upstream wine, and the later tags do not exist in their repository.
To be exact the version is wine-5.12-13989-gca3681631ad
, which means that it is 13989 commits after version 5.12, which aligns with the version 7.0
reported by winecfg
and wineserver -v
. Why tools like lutris are being silly and base their version checking on wine
and not wineserver
is beyond me. The version in wine
is derived by the build-system from the repository information at build-time, where wineserver
version is set by the developers.
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.