Package Details: proton-cachyos 1:10.0.20260228-1

Git Clone URL: https://aur.archlinux.org/proton-cachyos.git (read-only, click to copy)
Package Base: proton-cachyos
Description: A compatibility tool for Steam Play based on Wine and additional components, experimental branch with extra CachyOS flavour
Upstream URL: https://github.com/CachyOS/proton-cachyos
Licenses: custom
Provides: proton
Submitter: loathingkernel
Maintainer: loathingkernel (ptr1337)
Last Packager: loathingkernel
Votes: 10
Popularity: 0.21
First Submitted: 2024-11-01 10:46 (UTC)
Last Updated: 2026-03-11 16:00 (UTC)

Required by (6)

Sources (6)

Latest Comments

1 2 3 Next › Last »

Wyn commented on 2026-03-06 08:29 (UTC)

@solx123 If you spent 2 seconds reading the pkgbuid you would understand that you're compiling this. You can't just say I demand this to be deleted because you can't read smh.

Last thing you need is loathing loathing other things.

solx123 commented on 2026-03-02 18:49 (UTC)

okay i apologize for that it was not exactly my intention to attack you or the work

loathingkernel commented on 2026-03-02 18:21 (UTC) (edited on 2026-03-02 18:25 (UTC) by loathingkernel)

@solx123 It didn't build successfully because of changes in other packages that happened after the previous update, at the time it was building successfully

proof:

previous: https://github.com/loathingKernel/PKGBUILDs/actions/runs/21805661501

current: https://github.com/loathingKernel/PKGBUILDs/actions/runs/22554714940

just mention in description that this package exists to waste the time of those who try to build it

So far the only waste of time I see here is interacting with you. If you do not understand that you are building proton from source, which contains a large amount of other projects, that's on you. You are the one telling your computer what to do, you choose what you build, if that's not what you expect, the only person you can blame is yourself.

but the main issue was that the build failed after running for nearly half an hour

Then you should probably have led with that, instead of attacking the usefulness of the package itself.

solx123 commented on 2026-03-02 18:20 (UTC)

yeah i mean i do need it but the main issue was that the build failed after running for nearly half an hour

loathingkernel commented on 2026-03-01 12:13 (UTC) (edited on 2026-03-01 12:14 (UTC) by loathingkernel)

@solx123 there is an easy solution to that, don't build it if you don't need it. Or do you expect the AUR to cater to your incompetence of reading the PKGBUILD?

solx123 commented on 2026-03-01 08:17 (UTC)

this package needs to be taken down. this is a massive waste of time and cpu resource

txtsd commented on 2026-01-16 17:27 (UTC) 

The Meson build system
Version: 1.8.4
Source dir: /home/txtsd/.cache/yay/proton-cachyos/src/build/src-dxvk
Build dir: /home/txtsd/.cache/yay/proton-cachyos/src/build/obj-dxvk-i386
Build type: cross build
Project name: dxvk
Project version: 2.7.1
C compiler for the host machine: i686-w64-mingw32-gcc (gcc 15.2.0 "i686-w64-mingw32-gcc (GCC) 15.2.0")
C linker for the host machine: i686-w64-mingw32-gcc ld.bfd 2.45.1
C++ compiler for the host machine: i686-w64-mingw32-g++ (gcc 15.2.0 "i686-w64-mingw32-g++ (GCC) 15.2.0")
C++ linker for the host machine: i686-w64-mingw32-g++ ld.bfd 2.45.1
C compiler for the build machine: ccache cc (gcc 15.2.1 "cc (GCC) 15.2.1 20260103")
C linker for the build machine: cc ld.bfd 2.45.1
C++ compiler for the build machine: ccache c++ (gcc 15.2.1 "c++ (GCC) 15.2.1 20260103")
C++ linker for the build machine: c++ ld.bfd 2.45.1
Build machine cpu family: x86_64
Build machine cpu: x86_64
Host machine cpu family: x86
Host machine cpu: x86
Target machine cpu family: x86
Target machine cpu: x86
Looking for a fallback subproject for the dependency libdisplay-info because:
Use of fallback dependencies is forced.
ERROR: Subproject libdisplay-info is buildable: NO

src-dxvk/meson.build:51:18: ERROR: Subproject exists but has no meson.build file.

loathingkernel commented on 2025-09-15 10:02 (UTC) (edited on 2025-09-15 10:03 (UTC) by loathingkernel)

@iamkroot it doesn't, since it builds fine on my CI in clean chroots. It might require git-lfs due to system conf which is otherwise not present in a clean chroot.

1 2 3 Next › Last »