[jhalfs] 02/03: Pass tracking file to gen_pkg_book

"Git Owner" ([email protected] via alfs-discuss Mailing List) <[email protected]>
Newsgroups gmane.linux.lfs.automated
Message-ID <[email protected]>
This is an automated email from the git hooks/post-receive script.

git pushed a commit to branch trunk
in repository jhalfs.

commit b8e5cad4c0a1d49fbbf170b7683fadb141345c74
Author: Pierre Labastie <[email protected]>
AuthorDate: Thu Dec 16 13:50:33 2021 +0100

    Pass tracking file to gen_pkg_book
    
    This is needed for managing -pass1 packages, since their version
    can only be found in the tracking file (thanks to previous commit).
---
 BLFS/Makefile        |  2 +-
 BLFS/gen_pkg_book.sh | 10 +++++++---
 2 files changed, 8 insertions(+), 4 deletions(-)

diff --git a/BLFS/Makefile b/BLFS/Makefile
index 2a11fde..6ed9c61 100644
--- a/BLFS/Makefile
+++ b/BLFS/Makefile
@@ -95,7 +95,7 @@ ifneq ($(REV),sysv)
 endif
 
 $(BOOK_XML): $(CONFIG_OUT)
-	$(Q)$(TOPDIR)/gen_pkg_book.sh $(TOPDIR) $(BLFS_FULL) $(LFS_FULL)
+	$(Q)$(TOPDIR)/gen_pkg_book.sh $(TRACKFILE) $(TOPDIR) $(BLFS_FULL) $(LFS_FULL)
 
 $(CONFIG_OUT): $(CONFIG_CONFIG_IN)
 	$(Q)CONFIG_="" KCONFIG_CONFIG=configuration \
diff --git a/BLFS/gen_pkg_book.sh b/BLFS/gen_pkg_book.sh
index 482a61c..ade0da9 100755
--- a/BLFS/gen_pkg_book.sh
+++ b/BLFS/gen_pkg_book.sh
@@ -4,15 +4,19 @@
 #
 set -e
 
-TOPDIR=$1
+TRACKFILE=$1
+if test -z "$TRACKFILE"; then
+  TRACKFILE=/var/lib/jhalfs/BLFS/instpkg.xml
+fi
+TOPDIR=$2
 if test -z "$TOPDIR"; then
   TOPDIR=$(pwd)
 fi
-BLFS_FULL=$2
+BLFS_FULL=$3
 if test -z "$BLFS_FULL"; then
   BLFS_FULL=${TOPDIR}/blfs-xml/tmp/blfs-full.xml
 fi
-LFS_FULL=$3
+LFS_FULL=$4
 if test -z "$LFS_FULL"; then
   LFS_FULL=${TOPDIR}/lfs-xml/tmp/lfs-full.xml
 fi

-- 
To stop receiving notification emails like this one, please contact
the administrator of this repository.

-- 
http://lists.linuxfromscratch.org/sympa/info/alfs-discuss
Unsubscribe: See the above information page
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.