Package Details: proton-ge-custom-bin 1:GE_Proton10_34-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)
Last Packager: chaotic-aur
Votes: 272
Popularity: 4.13
First Submitted: 2020-02-21 11:06 (UTC)
Last Updated: 2026-04-06 11:55 (UTC)

Dependencies (27)

Required by (10)

Sources (5)

Pinned Comments

Latest Comments

1 2 3 4 5 6 .. 31 Next › Last »

saghm commented on 2026-04-28 16:43 (UTC)

@EpicTux123 every comment on here is sending a separate email to every person who has ever commented on this thread before (unless they decide to unsubscribe). I'm skeptical that it's worth mentioning every change to a PKGBUILD that is not actually the official one yet here; if it does become the official package, a single comment with a "release notes" style update (maybe pinned for visibility) would be reasonable, but right now everyone who is using the current version of the package has to decide between unsubscribing and risking not getting notifications about things with the package they might find useful or tolerating emails about every small change to a PKGBUILD they might never use.

Maybe it would make more sense to post the release notes at a URL on the same server you're hosting the PKGBUILD on and then update them there each time? People who are interested can check there periodically to see what the updates are, and those who would prefer to wait until they become relevant to the official package here can remain subscribed to the updates without needing the extra info they're not looking for.

michihupf commented on 2026-04-28 11:31 (UTC)

I don't think that assuming the PKGBUILD might be corrupt is a good argument for downloading the checksum file. I must say I myself have been a bit annoyed by your comments since I got like 8 emails in the last 2 days, so that might also play a role in me being so defensive on how this package was maintained previously. I apologize for that

EpicTux123 commented on 2026-04-28 11:23 (UTC) (edited on 2026-04-28 11:26 (UTC) by EpicTux123)

Hi michihupf,

Compared to the current package, the pkgrel was bumped only once due to many other differences (such as three files not being shipped anymore). It is not live yet, since I am waiting for the orphan request to complete. So, if the package is eventually owned by me, pkgrel would've been only bumped once (and I guess Proton-GE version 10-35 would be released by then anyways).

In regards to why check it twice: because the locally downloaded file may be corrupt somehow, so checking it twice (local checksum + upstream-provided checksum) is safer. I could skip the first check since we're going to do the second anyways, but I think it's fine to keep both since it doesn't really get into the way of installing the package (it does not delay it significantly).

I am registering my progress here so users of this package can know what has been changing. If I do become the maintainer, such changes will be in one or two commits instead of multiple commits like my previous comments.

I understand your criticism of "changes for changes sake", but I wanted to document it anyways as to not later appear with different parts of the PKGBUILD all of a sudden.

And, indeed, I am quite enthusiastic about it. It's the first package I am trying to maintain, and I believe I've been doing great by following the guidelines and such. :)

Thanks.

michihupf commented on 2026-04-28 11:18 (UTC) (edited on 2026-04-28 11:18 (UTC) by michihupf)

Even though I appreciate the enthusiasm some of these changes seem to just be "changes for changes sake" not really providing anything or improving on anything. Variable changes in the PKGBUILD don't warrant a pkgrel bump imo and considering the latest comment: Why check it twice? This seems like an unnecessary step...

EpicTux123 commented on 2026-04-28 11:07 (UTC)

Alright folks, new PKGBUILD in town once again!

A bit of a "major" upgrade this one: now it also performs a download of the dot sha512sum file provided by upstream and re-validates against it as well, in addition to the local checksum validation (that is, it checks the Proton-GE .tar.gz twice). If it fails, the entire process quits, as a safety measure.

Additionally, "proton.orig" created from the "patch" command is now deleted, since it is not needed (it just serves as a backup for the file before the patch).

https://paste.coalserver.de/?d53e1d8a2551de7d#6e8yANKcf3eG55Wf6bpDSkYTnPb1L3Ny4Yep9kg8x3NR

EpicTux123 commented on 2026-04-28 07:37 (UTC)

Another minor update. Removed custom variable "_pkgname" and replaced instances where it was used (it was a variable to take "proton-ge-custom-bin" and remove the "-bin" suffix). This way, the URL field now is a clickable/copyable field.

https://paste.coalserver.de/?38611f313e527e10#GXFp3XEAJFhHm74rMnCSD5MLHM9DFLAjtzCn6aMysdiQ

For now, there should not be any new updates to the PKGBUILD aside from new upstream releases.

I was thinking of adding something like "rm -f /usr/share/steam/compatibilitytools.d/proton-ge-custom-bin/proton.orig" to delete the backup file that is created when using the "patch" command, but since it's a small 100 KB file I believe it's better to keep it as to let people know, when viewing that directory, that the original "proton" file was modified. Let me know if you think it should be deleted instead.

Thanks.

EpicTux123 commented on 2026-04-28 03:30 (UTC)

Minor update to the PKGBUILD; now preserves the licenses in /usr/share/steam/compatibilitytools.d/ as well; files in /usr/share/licenses/ are now symbolic links (instead of moving the files).

https://paste.coalserver.de/?9fb9189f872eaae2#EvCM9vojLG31P8TeRcRa9YxqGPNfoTWzsGYCcytVtHhW

EpicTux123 commented on 2026-04-27 18:48 (UTC)

I've updated the PKGBUILD file with some miscellaneous changes (notably the name convention) as well as to include an explanation for the patch file.

https://paste.coalserver.de/?245d1d24d4bbf884#Ffyt8RxZzuj99EmqRoG1PzXqn3WdJ6byDQrW9pVUYrb4

It's this one that I intend to use if I become the maintainer of this package.

Aditionally, I've added some safety notes for the dot install file for pre-upgrade, since the folder to which the package is installed is now different due to name conventions, and I'm not sure if everything will be correctly dealt with.

Dot install file: https://paste.coalserver.de/?3391c00555ab13fe#CfWNi2jCNP5qY6SN5RLF18uzmjLNfjpkbGNg6tf2cwWK

Thanks.

pussyhut commented on 2026-04-27 14:41 (UTC)

@PedroHLC Got it. Sad to hear you're leaving, wish you all best.

PedroHLC commented on 2026-04-27 14:29 (UTC)

I indeed haven't used Arch Linux since Dec. 2021 and would sporadically run a Podman container merely to fix this PKGBUILD build when needed, not actually testing or actively trying to enhance it. I don't know EpicTux123; I only know he's a fellow Brazilian but have no reason to distrust him. Anyway, I disowned this package in the hope it brings some fresh new eyes over it.

1 2 3 4 5 6 .. 31 Next › Last »