From 726b8d4375ccec67be33b4ad3dbcacc6268eea05 Mon Sep 17 00:00:00 2001
From: Theo Buehler <tb@cvs.openbsd.org>
Date: Wed, 14 Aug 2019 20:30:20 +0000
Subject: Explain how to take over syspatch builds from another machine.

ok ajacoutot robert
---
 distrib/syspatch/README | 20 ++++++++++++++++++--
 1 file changed, 18 insertions(+), 2 deletions(-)

diff --git a/distrib/syspatch/README b/distrib/syspatch/README
index f48c6738270..52f5da5d719 100644
--- a/distrib/syspatch/README
+++ b/distrib/syspatch/README
@@ -1,4 +1,4 @@
-$OpenBSD: README,v 1.3 2017/11/05 10:29:24 rpe Exp $
+$OpenBSD: README,v 1.4 2019/08/14 20:30:19 tb Exp $
 
 Notes about the syspatch(8) build process
 =========================================
@@ -28,7 +28,7 @@ and find differing files between patched releases.
 
 e.g.
 FAKEROOT=/fakeroot
-FAKE=${FAKEROOT}/syspatch/61-000_release
+FAKE=${FAKEROOT}/syspatch/64-000_release
 RELEASEDIR=/path/to/sets
 mkdir -p ${FAKE}
 install -m 0700 ${RELEASEDIR}/bsd{,.mp} ${FAKE}
@@ -39,6 +39,22 @@ mkdir -m 700 -p ${FAKE}/usr/share/relink/kernel/GENERIC{,.MP}
 tar -C ${FAKE}/usr/share/relink/kernel -xzf ${FAKE}/usr/share/relink/kernel.tgz
 rm ${FAKE}/usr/share/relink/kernel.tgz
 
+Continuing syspatch builds
+--------------------------
+
+If syspatches were already built for this release on a different machine, the
+following additional steps are required. Prepare a ${SYSPATCHES} directory
+containing all the syspatches of the release. Make a copy of the ${FAKE}
+directory and extract all the syspatches in it.
+
+e.g.
+SYSPATCHES=/path/to/syspatches
+PATCHED=${FAKEROOT}/syspatch/64-018_mds
+cp -Rp ${FAKE} ${PATCHED}
+for _s in ${SYSPATCHES}/*.tgz; do tar -C ${PATCHED} -xzphf ${_s}; done
+
+Then apply all the errata patches to the source trees.
+
 Building a syspatch
 -------------------
 
-- 
cgit v1.2.3