janware/jw-pkg
Watch
1
Code Pull requests Activity Actions

py-ns-dir.mk: Fix PY_UPDATE_INIT_PY ?= false
All checks were successful
CI / Packaging - Kali Linux (pull_request) Successful in 6m1s
Details
CI / Packaging - OpenSUSE Tumbleweed (pull_request) Successful in 4m58s
Details
CI / Packaging test (pull_request) Successful in 0s
Details
CI / Packaging - Kali Linux (push) Successful in 9m14s
Details
CI / Packaging - OpenSUSE Tumbleweed (push) Successful in 4m35s
Details
CI / Packaging test (push) Successful in 0s
Details

Browse source 
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 <jan@janware.com>
This commit is contained in:
Jan Lindemann 2026-09-20 17:43:04 +02:00
commit 465b9f5461
Signed by: Jan Lindemann
GPG key ID: 3750640C9E25DD61
1 changed files with 1 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

2
make/py-ns-dir.mk
View file

@ -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)