Package Details: wine-ge-custom 6.21.GE.1-2

Git Clone URL: https://aur.archlinux.org/wine-ge-custom.git (read-only, click to copy)
Package Base: wine-ge-custom
Description: A compatibility layer for running Windows programs - GloriousEggroll branch
Upstream URL: https://github.com/GloriousEggroll/wine-ge-custom
Licenses: LGPL
Conflicts: wine, wine-wow64
Provides: wine=6.21, wine-wow64=6.21
Submitter: loathingkernel
Maintainer: loathingkernel
Last Packager: loathingkernel
Votes: 4
Popularity: 1.71
First Submitted: 2021-09-01 22:06
Last Updated: 2021-11-27 22:36

Dependencies (141)

Required by (306)

Sources (8)

Latest Comments

1 2 Next › Last »

ptr1337 commented on 2021-10-19 09:31

Prebuilt packages can be found here: https://mirror.cachyos.org/?search=wine

how to add this repo:

https://wiki.cachyos.org/en/home/Repo

The packages are built with x86-64 and the optimized x86-64-v3 if your cpu supports that.

loathingkernel commented on 2021-10-15 11:14

@thaewrapt Yes, it is a replacement for regular wine, which can also be used in Lutris as it supports using the system-wide wine.

thaewrapt commented on 2021-10-15 10:56

@loathingkernel Yeah, I see your point as well. With lutris only looking into ~/.local directory for its runners, a possible way is to have a system-wide installation (either in the form of tar archive or extracted) with a shell script that should be run by the enduser from their own gaming account to update local runners directory with a current version from system-wide distribution. Or, as an alternative, one could use a third party script which will just plain download the latest version (or the version of choice) from github releases and put it directly inside the same runners directory.

But, anyway, this is offtopic to this particular AUR package, I guess (as it just provides the alternative to a system-wide wine, correct?).

loathingkernel commented on 2021-10-15 10:01

@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.

thaewrapt commented on 2021-10-15 09:11

@loathingkernel I think he's talking about wine-ge-custom-bin package (or however it could be called), meaning automated installation of the prebuilt binaries from https://github.com/GloriousEggroll/wine-ge-custom/releases

loathingkernel commented on 2021-10-07 12:05

@Tomoghno nope, there are repos packaging this PKGBUILD out there, you can use one of those. Also, PKGBUILDs packaging the binary results of other PKGBUILDs are STRICTLY prohibited in the AUR.

Tomoghno commented on 2021-10-07 11:56

Can You Make a Binary Package for it ...

loathingkernel commented on 2021-09-27 15:06

@kenga I moved a few environment variables around and it should be ok with yay too now. That being said I still believe that the assumptions yay is making are wrong and they definitely are not the default behavior of makepkg. Just something to keep in mind if other issues arise with it.

kenga commented on 2021-09-27 14:48

Yep, building directly with makepkg seems to work. Quite annoying, as yay had been playing nice so far.

Well, time to retire yet another helper I suppose...

loathingkernel commented on 2021-09-26 23:13

I don't know what shitty things yay is doing and why but it doesn't follow the assumed makepkg way and it doesn't retain the environment between prepare() and build() as evident by the existence of filtered flags in your log. My guess is that it first prepares the sources and then starts the build again with a new environment for some reason.

Package builds fine in a clean chroot with Arch's proper tooling.