Package Details: proton-ge-custom-bin 1:GE_Proton9_4-1

Git Clone URL: https://aur.archlinux.org/proton-ge-custom-bin.git (read-only, click to copy)
Package Base: proton-ge-custom-bin
Description: A fancy custom distribution of Valves Proton with various patches
Upstream URL: https://github.com/GloriousEggroll/proton-ge-custom
Keywords: d9vk DXVK Faudio GloriousEggroll MediaFoundation Proton protonfixes Steam System-wide Valve vkd3d Wine
Licenses: custom, BSD, MPL, LGPL, MIT, zlib
Conflicts: proton-ge-custom
Provides: proton, proton-ge-custom
Submitter: RogueGirl
Maintainer: Jaja (floriplum, chaotic-aur, PedroHLC)
Last Packager: chaotic-aur
Votes: 201
Popularity: 4.47
First Submitted: 2020-02-21 11:06 (UTC)
Last Updated: 2024-04-15 19:28 (UTC)

Pinned Comments

PedroHLC commented on 2021-07-27 19:39 (UTC)

The "chaotic-aur" co-maintainer is a bot that pulls any merged PR in https://github.com/chaotic-aur/pkgbuild-proton-ge-custom-bin back to this package. So if you guys have contributions or bump versions earlier than the maintainer, please share them as PRs. The commits will keep your authorship.

Happy gaming!

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 9 .. 25 Next › Last »

ChrisLane commented on 2022-04-06 08:49 (UTC)

I've not had any problems running GE-Proton7-14 installed using the following diff

diff --git a/PKGBUILD b/PKGBUILD
index 6dcb71b..6a9c79f 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -10,7 +10,7 @@
 ## pkginfo
 pkgdesc='A fancy custom distribution of Valves Proton with various patches'
 pkgname=proton-ge-custom-bin
-pkgver=GE_Proton7_10
+pkgver=GE_Proton7_14
 pkgrel=1
 epoch=1
 arch=('x86_64')
@@ -69,7 +69,7 @@ backup=("${_protoncfg}")
 url='https://github.com/GloriousEggroll/proton-ge-custom'
 source=("${_pkgver}_${pkgrel}.tar.gz::${url}/releases/download/${_pkgver}/${_pkgver}.tar.gz"
    'supplementary.tar.zst')
-sha512sums=('1d105a3df5c3fca115f390232dbed0a8f8180fba50027437ab59640277628d0831b3d5c598a585bc1df4ed127638163e3520524553e51650128b70e1b4e1bb3d'
+sha512sums=('3cbe99a2659dab1871cef0b50deb8cab4f101cc4d0531ed3d2cd7cf89dcee6aa08357b3d485e4260ab7a46af13bf6349daed16deb382cbadd5b2831ba7ad5503'
             'a484c4cd2003057cf0cbbd32ca5d0106e97c75434e7bef34b35be8239ad98a482358852e41e85abedf5b24ac4d0375c8fffc7deee81a9b08c7799a398f23773b')

 build() {

Jaja commented on 2022-04-05 23:55 (UTC)

@vkulikov i'm currently not having access to an arch box but will be updating saturday, if nobody steps up earlier.

vkulikov commented on 2022-04-05 08:11 (UTC)

any updates soon? seems, stable version is ready https://github.com/GloriousEggroll/proton-ge-custom/releases/tag/GE-Proton7-14

fabiscafe commented on 2022-04-04 16:58 (UTC)

@Zeros Proton requires the Steam "sandbox" (not an actual sandbox, but I don't know a better name for it). That's why Lutris doesn't support proton anymore, for a longer time. You might want wine-ge -> https://github.com/GloriousEggroll/wine-ge-custom/releases

Zeros commented on 2022-04-03 20:55 (UTC)

Anyway to also have Lutris see this package as an available runner?

Jaja commented on 2022-03-08 21:00 (UTC)

@PedroHLC Yes, true words. But havings files other than PKGBUILD, SRCINFO and maybe changelog uploaded to aur is considered a bad thing. It is kind of an abuse of the service instead of hosting files upstream or somewhere else.. I wanted to keep the impact low by having only one tiny compressed file. Anyway - if you are sure it's not going to cause trouble i would happily extract. Would be easier for me as well..

proledatarian commented on 2022-03-08 13:27 (UTC) (edited on 2022-03-08 13:29 (UTC) by proledatarian)

I always get the following error using an AUR-helper. Is it just me or is this an issue with the PKGBUILD? Building the package manually works though.

-> error fetching proton-ge-custom-bin: fatal: not a git repository (or any parent up to mount point /)
Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).
context: exit status 128

PedroHLC commented on 2022-03-08 11:05 (UTC)

Putting extra files in a ".tar.zst" is not very common. Usually, we keep extracted, for (one) it's quick to inspect, and (two) they're correctly versioned (aur uses git, and it can't diff blobs properly).

So, if you ever need to update this file's contents, consider extracting them.

blueman commented on 2022-02-28 20:21 (UTC)

@Jaja: Thanks for the explaination and I agree, it makes sense.