From 465b9f54610b5034dcfa04757ccd924f0b4d00cc Mon Sep 17 00:00:00 2001 From: Jan Lindemann Date: Sun, 20 Sep 2026 17:43:04 +0200 Subject: [PATCH] py-ns-dir.mk: Fix PY_UPDATE_INIT_PY ?= false The commit message of 29abf14a6 clearly states As of this commit, this is the case by default, i.e. PY_UPDATE_INIT_PY is set to false in py-ns-dir.mk, maintaining the current behaviour. The commit's diff then proceeds to set PY_UPDATE_INIT_PY to true. Which is a clear-cut case of my brain doing something different from what my fingers do. Correcting the commit. Some downstream projects have already consumed this blunder. Not quite sure where that leaves us, but we need to start somewhere with fixing, so I decide to make the code match the documented behaviour, and wait for the fallout to fix. Signed-off-by: Jan Lindemann --- make/py-ns-dir.mk | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/make/py-ns-dir.mk b/make/py-ns-dir.mk index 3529e721..44ee6024 100644 --- a/make/py-ns-dir.mk +++ b/make/py-ns-dir.mk @@ -5,7 +5,7 @@ __path__ = extend_path(__path__, __name__) endef # The __init__.py machinery duplicates (but is independent from) py-mod.mk -PY_UPDATE_INIT_PY ?= true +PY_UPDATE_INIT_PY ?= false PY_INSTALL_INIT_PY ?= false ifneq ($(PY_UPDATE_INIT_PY),false)