heads/patches/bash-5.1.16.patch

--- clean/bash-5.1.16/Makefile.in	2020-12-16 16:13:10.000000000 -0600
+++ bash-5.1.16/Makefile.in	2023-04-25 14:16:38.849618679 -0600
@@ -626,7 +626,7 @@
 	@${MAKE} ${MFLAGS} tests TESTSCRIPT=run-gprof
 
 version.h:  $(SOURCES) config.h Makefile patchlevel.h
-	$(SHELL) $(SUPPORT_SRC)mkversion.sh -b -S ${topdir} -s $(RELSTATUS) -d $(Version) -o newversion.h \
+	$(SHELL) $(SUPPORT_SRC)mkversion.sh -S ${topdir} -s $(RELSTATUS) -d $(Version) -o newversion.h \
 		&& mv newversion.h version.h
 
 bashversion$(EXEEXT): buildversion.o $(SUPPORT_SRC)bashversion.c
patches/bash-5.1.16.patch: Do not increment build number Bash uses .build to keep count of the build number, which conflicts with heads build system usage of .build to keep track of built modules. If .build already exists when bash/configure is run it will increment by 1 the build number. This is configurable on the call to the support script support/mkversion.sh, which is called from the bash/Makefile. Patching the Makefile template used during bash configuration allows disabling the build number increment. Signed-off-by: Daniel Pineda <daniel.pineda@puri.sm> 2023-04-25 20:32:25 +00:00			`--- clean/bash-5.1.16/Makefile.in 2020-12-16 16:13:10.000000000 -0600`
			`+++ bash-5.1.16/Makefile.in 2023-04-25 14:16:38.849618679 -0600`
			`@@ -626,7 +626,7 @@`
			`@${MAKE} ${MFLAGS} tests TESTSCRIPT=run-gprof`

			`version.h: $(SOURCES) config.h Makefile patchlevel.h`
			`- $(SHELL) $(SUPPORT_SRC)mkversion.sh -b -S ${topdir} -s $(RELSTATUS) -d $(Version) -o newversion.h \`
			`+ $(SHELL) $(SUPPORT_SRC)mkversion.sh -S ${topdir} -s $(RELSTATUS) -d $(Version) -o newversion.h \`
			`&& mv newversion.h version.h`

			`bashversion$(EXEEXT): buildversion.o $(SUPPORT_SRC)bashversion.c`