chore: 1.2.0
Steam's autoscroll stops depending on -noverifyfiles: the patch is written at the size and timestamp Steam recorded, so the client's own file check finds nothing to repair and the flag survives whichever way Steam was started. An installation patched by 1.1.0 is redone at the original size on the next apply. Also picks up the launch paths that were never covered - shortcuts on the desktop, Steam as a Flatpak, steam-native and steam-jupiter.
This commit is contained in:
1 parent
b7e0ff6fd1
commit
af82ffec78
1 file changed
+1
-1
@@ -8,7 +8,7 @@
|
||||
# Overridable so a packager can pass the version it is actually building
|
||||
# (`make VERSION=$pkgver`). The literal below is the fallback for builds
|
||||
# straight from a checkout, and is what a release tag has to carry.
|
||||
VERSION ?= 1.1.0
|
||||
VERSION ?= 1.2.0
|
||||
|
||||
PREFIX ?= /usr
|
||||
DESTDIR ?=
|
||||
|
||||
Reference in new issue
Block a user