From: Adolf Belka <adolf.belka@ipfire.org>
To: development@lists.ipfire.org
Cc: Adolf Belka <adolf.belka@ipfire.org>
Subject: [PATCH] readline: Change the VER parameter to also include the patch number
Date: Wed, 28 Oct 2026 21:47:00 +0100 [thread overview]
Message-ID: <20261028204700.2431586-2-adolf.belka@ipfire.org> (raw)
In-Reply-To: <20261028204700.2431586-1-adolf.belka@ipfire.org>
- There was a separate VER and PATCHVER number and when building only the VER part was
shown, 8.3 in the readline case.
- With this change 8.3.6 is now shown, combining the package and patch version
- The other changes are to use the appropriate parts of the new VER parameter THISAPP
and the application of the patches.
Signed-off-by: Adolf Belka <adolf.belka@ipfire.org>
---
lfs/readline | 12 ++++++------
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/lfs/readline b/lfs/readline
index 37769c2ca..b8589c4b9 100644
--- a/lfs/readline
+++ b/lfs/readline
@@ -24,11 +24,11 @@
include Config
-VER = 8.3
-PATCHVER = 6
+VER = 8.3.6
+
# https://ftp.gnu.org/gnu/readline/
-THISAPP = readline-$(VER)
+THISAPP = readline-$(basename $(VER))
DL_FILE = $(THISAPP).tar.gz
DL_FROM = $(URL_IPFIRE)
DIR_APP = $(DIR_SRC)/$(THISAPP)
@@ -73,9 +73,9 @@ $(TARGET) : $(patsubst %,$(DIR_DL)/%,$(objects))
@$(PREBUILD)
@rm -rf $(DIR_APP) && cd $(DIR_SRC) && tar zxf $(DIR_DL)/$(DL_FILE)
-ifneq "$(PATCHVER)" "0"
- for i in $$(seq 1 $(PATCHVER)); do \
- cd $(DIR_APP) && patch -Np0 < $(DIR_SRC)/src/patches/readline/readline$(subst .,,$(VER))-$$(printf "%03d" "$${i}") || exit 1; \
+ifneq ($(suffix $(VER)),.0)
+ for i in $$(seq 1 $(patsubst .%,%,$(suffix $(VER)))); do \
+ cd $(DIR_APP) && patch -Np0 < $(DIR_SRC)/src/patches/readline/readline$(subst .,,$(basename $(VER)))-$$(printf "%03d" "$${i}") || exit 1; \
done
endif
--
2.56.0
prev parent reply other threads:[~2026-10-28 20:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-28 20:46 [PATCH] bash: " Adolf Belka
2026-10-28 20:47 ` Adolf Belka [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20261028204700.2431586-2-adolf.belka@ipfire.org \
--to=adolf.belka@ipfire.org \
--cc=development@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox