From c777e8280dbeaebbe7cd0ad8c835e509fb80dd3b Mon Sep 17 00:00:00 2001 From: Felitendo Date: Sun, 6 Sep 2026 14:00:43 +0200 Subject: [PATCH] chore: 1.4.0 Steam's helper script is only patched when the patch keeps the file at the length Steam wrote down. Where the comments cannot pay for the argument, nothing is written at all: a file of the wrong length costs the whole client package downloaded and installed again, and a client that quits at the end of it instead of coming up. With no such patch left to prop up, -noverifyfiles is gone from everything that carried it - Steam's launcher entry, its autostart entry, the shortcut on the desktop and the ones Steam writes for single games. Steam repairs its own installation again, and nothing of this program's is on its command line. A patch an earlier version appended is rebuilt to fit at the next apply, or taken back if it cannot be. A script somebody puts in front of the client to add a switch of its own is recognised as a way of starting Steam, rather than as an application to hand the flag to. A desktop entry edited in place that the ledger has lost is written again from the copy kept beside it. Without that, an entry from an older version kept an older answer for good - a browser patched that way stayed on the flag that shows the "unsupported command-line flag" bar while every other browser moved off it in 1.3.0. --- Makefile | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Makefile b/Makefile index cf1178d..4f43e8e 100644 --- a/Makefile +++ b/Makefile @@ -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.3.0 +VERSION ?= 1.4.0 PREFIX ?= /usr DESTDIR ?=