Skip to contentSkip to conversation

setlocalversion: do not append git commit hash if localversion* exists

PATCH In review Masahiro Yamada 1 participant 3 messages Jan 31, 2023 – Feb 5, 2023 Kbuild

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 setlocalversion: do not append git commit hash if localversion* exists

Since commit dcfbcb1033bb ("setlocalversion: use only the correct release tag for git-describe"), KERNELRELEASE of linux-next is annoyingly long:

  $ make kernelrelease
  6.2.0-rc6-next-20230131-09515-g80bd9028feca

The string '-09515-g80bd9028feca' is appended because git-describe now uses the v6.2.0 tag instead of the next-20230113 tag.

In linux-next, the 'localversion-next' file well specifies the local version, so the extra info from git is unneeded.

---

 scripts/setlocalversion | 21 +++++++++++----------
 1 file changed, 11 insertions(+), 10 deletions(-)
scripts/setlocalversion +11 -10
index e2b2d492ac13..4219a0ca1e62 100755
@@ -113,22 +113,23 @@ if [ -z "${KERNELVERSION}" ]; then
 	exit 1
 fi
 
-res="${KERNELVERSION}"
-
 # localversion* files in the build and source directory
-res="${res}$(collect_files localversion*)"
+file_localversion="$(collect_files localversion*)"
 if test ! "$srctree" -ef .; then
-	res="$res$(collect_files "$srctree"/localversion*)"
+	file_localversion="${file_localversion}$(collect_files "$srctree"/localversion*)"
 fi
 
-# CONFIG_LOCALVERSION and LOCALVERSION (if set)
+# CONFIG_LOCALVERSION
 config_localversion=$(sed -n 's/^CONFIG_LOCALVERSION=\(.*\)$/\1/p' include/config/auto.conf)
-res="${res}${config_localversion}${LOCALVERSION}"
 
 # scm version string if not at the kernel version tag
-if grep -q "^CONFIG_LOCALVERSION_AUTO=y$" include/config/auto.conf; then
+if [ -n "${file_localversion}" ]; then
+	# If localversion* files exist (like in linux-next), the version is
+	# well specified. Do not append scm_version.
+	scm_version=
+elif grep -q "^CONFIG_LOCALVERSION_AUTO=y$" include/config/auto.conf; then
 	# full scm version string
-	res="$res$(scm_version)"
+	scm_version="$(scm_version)"
 elif [ "${LOCALVERSION+set}" != "set" ]; then
 	# If the variable LOCALVERSION is not set, append a plus
 	# sign if the repository is not in a clean annotated or
@@ -137,7 +138,7 @@ elif [ "${LOCALVERSION+set}" != "set" ]; then
 	#
 	# If the variable LOCALVERSION is set (including being set
 	# to an empty string), we don't want to append a plus sign.
-	res="$res$(scm_version --short)"
+	scm_version="$(scm_version --short)"
 fi
 
-echo "$res"
+echo "${KERNELVERSION}${file_localversion}${config_localversion}${LOCALVERSION}${scm_version}"
Signature · 1 line
2.34.1
#1 lore raw
Quoted 10 lines · Masahiro Yamada

Since commit dcfbcb1033bb ("setlocalversion: use only the correct release tag for git-describe"), KERNELRELEASE of linux-next is annoyingly long:

  $ make kernelrelease
  6.2.0-rc6-next-20230131-09515-g80bd9028feca

The string '-09515-g80bd9028feca' is appended because git-describe now uses the v6.2.0 tag instead of the next-20230113 tag.

v6.2.0 -> v6.2-rc6

Quoted 59 lines

In linux-next, the 'localversion-next' file well specifies the local version, so the extra info from git is unneeded.

---

 scripts/setlocalversion | 21 +++++++++++----------
 1 file changed, 11 insertions(+), 10 deletions(-)
scripts/setlocalversion +11 -11
index e2b2d492ac13..4219a0ca1e62 100755
@@ -113,22 +113,23 @@ if [ -z "${KERNELVERSION}" ]; then
        exit 1
 fi
 
-res="${KERNELVERSION}"
-
 # localversion* files in the build and source directory
-res="${res}$(collect_files localversion*)"
+file_localversion="$(collect_files localversion*)"
 if test ! "$srctree" -ef .; then
-       res="$res$(collect_files "$srctree"/localversion*)"
+       file_localversion="${file_localversion}$(collect_files "$srctree"/localversion*)"
 fi
 
-# CONFIG_LOCALVERSION and LOCALVERSION (if set)
+# CONFIG_LOCALVERSION
 config_localversion=$(sed -n 's/^CONFIG_LOCALVERSION=\(.*\)$/\1/p' include/config/auto.conf)
-res="${res}${config_localversion}${LOCALVERSION}"
 
 # scm version string if not at the kernel version tag
-if grep -q "^CONFIG_LOCALVERSION_AUTO=y$" include/config/auto.conf; then
+if [ -n "${file_localversion}" ]; then
+       # If localversion* files exist (like in linux-next), the version is
+       # well specified. Do not append scm_version.
+       scm_version=
+elif grep -q "^CONFIG_LOCALVERSION_AUTO=y$" include/config/auto.conf; then
        # full scm version string
-       res="$res$(scm_version)"
+       scm_version="$(scm_version)"
 elif [ "${LOCALVERSION+set}" != "set" ]; then
        # If the variable LOCALVERSION is not set, append a plus
        # sign if the repository is not in a clean annotated or
@@ -137,7 +138,7 @@ elif [ "${LOCALVERSION+set}" != "set" ]; then
        #
        # If the variable LOCALVERSION is set (including being set
        # to an empty string), we don't want to append a plus sign.
-       res="$res$(scm_version --short)"
+       scm_version="$(scm_version --short)"
 fi
 
-echo "$res"
+echo "${KERNELVERSION}${file_localversion}${config_localversion}${LOCALVERSION}${scm_version}"
--

2.34.1

Signature · 2 lines
Best Regards
Masahiro Yamada
#2 lore raw
In reply to Masahiro Yamada
Quoted 8 lines · Masahiro Yamada

Since commit dcfbcb1033bb ("setlocalversion: use only the correct release tag for git-describe"), KERNELRELEASE of linux-next is annoyingly long:

  $ make kernelrelease
  6.2.0-rc6-next-20230131-09515-g80bd9028feca
Quoted 8 lines

The string '-09515-g80bd9028feca' is appended because git-describe now uses the v6.2.0 tag instead of the next-20230113 tag.

In linux-next, the 'localversion-next' file well specifies the local version, so the extra info from git is unneeded.

---

I will drop this patch,
and send an alternative one.

Signature · 2 lines
Best Regards
Masahiro Yamada