Arch Linux User Repository

Alternative dependency wine-valve-git is orphaned and is hardcoded to proton-5.0 branch.

updated (by copying from proton) - builds for me but as with proton, i'm not 100% convinced it's all right now

This package is failing because of the same reasons the proton package used to fail: https://aur.archlinux.org/packages/proton/#comment-746010

Should be an easy fix.

It's failing because it's trying to used sed on a folder. sed -i 's/openvr_v0.9.16//g' vrclient_x64/vrclient_x64/* can be changed to sed -i 's/openvr_v0.9.16//g' vrclient_x64/vrclient_x64/*.* to resolve the issue.

I am not sure if this whole thing is necessary though.

Edit: Oh and I get a compiler error:

winegcc -c -march=x86-64 -mtune=generic -O2 -pipe -fno-plt  -I. -DSTEAM_API_EXPORTS  -o steamclient_main.o steamclient_main.c
steamclient_main.c:13:10: fatal error: wine/list.h: No such file or directory
   13 | #include "wine/list.h"
      |          ^~~~~~~~~~~~~
compilation terminated.
winegcc: /usr/bin/gcc failed
make: *** [Makefile:347: steamclient_main.o] Error 2

@EndlessEden, Same here.

Wont build; sed: couldn't edit vrclient_x64/vrclient_x64/json: not a regular file

I think this package requires xorgproto now.

Hi, there seems to be a version problem when upgrading from proton-git v7.0.1 to proton-git v8.0.1 after pacman builds and installs the package, pacman says the new package is still v7.0.1 and not v8.0.1

What can I do to remedy this? Thanks. Dave.

@Rulatir @Kyatik @rabcor Ideally this package would allow you to use a local build of proton within Steam per the instructions on the Github page. I haven't had a chance to go through the PKGBUILDs so this package make not install everything needed to do this yet.

I'll have to go through the PKGBUILDs of this, proton-git, and the proton package. Ideally, you could simply symlink a folder into ~/.steam/root/compatibilitytools.d/ and be able to use the latest/customized proton.

@Rulatir

you better to ask @JoshH100, I just made his proton package to use git, and abandoned it in flavor of him.

@yurikoles

THIRDING the question asked by @rabcor and @Kyatik

@yurikoles

How exactly does this package work? Proton is typically bundled with (and run through) steam, is this an independent package, e.g. will I be able to run applications through some command like $proton instead of $wine to use proton instead?

(copied from rabcor's comment because not answered)

How exactly does this package work? Proton is typically bundled with (and run through) steam, is this an independent package, e.g. will I be able to run applications through some command like $proton instead of $wine to use proton instead?

If I want to use the proton installation compiled by this package with steam, how would I go about it?

Version issue is now fixed.

Edit PKGBUILD and change pkgver() to following code as mentioned in the https://wiki.archlinux.org/index.php/VCS_package_guidelines

pkgver() {
  local version count

  cd "${pkgname}"

  version="$(git describe --abbrev=0 --tags | sed 's/\([^-]*-g\)/r\1/;s/-/./g')"
  count="$(git rev-list --count $(git describe --abbrev=0 --tags)..)"
  printf '%s.%s' "${version#proton-3.7*-}" "${count}"
}

@yurikoles

==> ERROR: pkgver is not allowed to contain colons, forward slashes, hyphens or whitespace. ==> ERROR: pkgver() generated an invalid version: proton-3.16beta-20181016.7 ==> ERROR: Makepkg was unable to build proton-git.

@zfkerr, thanks, fixed!

@yurikoles

      ==> Entering fakeroot environment...
      ==> Starting package()...
      install: cannot stat 'dist.LICENSE.lin': No such file or directory
      ==> ERROR: A failure occurred in package().
          Aborting...
      ==> ERROR: Makepkg was unable to build proton-git.

@Kiwii I'm not sure, you better to ask @Forty-Bot in proton package, I had just modified it to compile from branch insteam of release.

So, what do you have to do with a wine prefix to get a game in Wine to use the lsteamclient.dll.so and communicate with the native Steam? Does it need any overrides or do I have to copy dll files from the native Steam client's legacycompat folder somewhere?

Or am I vastly misunderstanding the intention of this package?