protontricks
https://github.com/Matoking/protontricks
A simple wrapper that does winetricks things for Proton enabled games.
- Devel package for openSUSE:Factory
-
2
derived packages
- Links to openSUSE:Factory / protontricks
- Download package
-
Checkout Package
osc -A https://api.opensuse.org checkout games:tools/protontricks && cd $_ - Create Badge
Refresh
Refresh
Source Files (show merged sources derived from linked package)
| Filename | Size | Changed |
|---|---|---|
| 0001-Fix-using-local-vdf-module.patch | 0000002297 2.24 KB | |
| _link | 0000000124 124 Bytes | |
| _service | 0000000544 544 Bytes | |
| protontricks-1.12.0.tar.xz | 0001011264 988 KB | |
| protontricks.changes | 0000012935 12.6 KB | |
| protontricks.spec | 0000001996 1.95 KB |
Comments 9
Hey, will this ever make its way into Factory (main TW repos)?
Nobody knows. Any reason why games repo is not good enough?
I didn't mean to ask as if the games repo is not good enough, just the fact that a separate repo has to be enabled in order to install protontricks.
Most games are only in games repo, so I personally usually don't feel the need to push to Factory. For other tools it's different. If you find/convince somebody willing to care (i.e. a maintainer :-), then it's probably as simply as a push to Factory, some tweaking when they have comments and that's it.
That depends on whether someone has the time to spare to maintain the package there, i.e. update the package and in case of bugs investigate and fix the problem or if not possible open tickets at the github project.
This now pulls in python310 since the last revision
I cannot reproduce this issue - on 15.4 and 15.5 it pulls python3-base, which depends on python3.6 (see https://build.opensuse.org/projects/games:tools/packages/protontricks/repositories/15.5/binaries/x86_64/protontricks-1.10.5-lp155.6.1.noarch.rpm) and on tumbleweed, python311-base (see https://build.opensuse.org/projects/games:tools/packages/protontricks/repositories/openSUSE_Tumbleweed/binaries/x86_64/protontricks-1.10.5-6.1.noarch.rpm)
If this issue persists, please provide more information how to reproduce.
Hello, the package is currently behind the release as 1.12.0 came out 3 weeks ago, will the package be updated to reflect the update ? Thanks in advance
The package has been updated to 1.12.0