Tue Jun 2 20:03:09 2020 UTC ()
doc/guide: there is no traditional non-pbulk bulk build anymore


(rillig)
diff -r1.30 -r1.31 pkgsrc/doc/guide/files/bulk.xml
cvs diff -r1.30 -r1.31 pkgsrc/doc/guide/files/bulk.xml (expand / switch to unified diff)

--- pkgsrc/doc/guide/files/bulk.xml 2020/05/30 19:25:17 1.30
+++ pkgsrc/doc/guide/files/bulk.xml 2020/06/02 20:03:09 1.31
@@ -1,14 +1,14 @@ @@ -1,14 +1,14 @@
1<!-- $NetBSD: bulk.xml,v 1.30 2020/05/30 19:25:17 rillig Exp $ --> 1<!-- $NetBSD: bulk.xml,v 1.31 2020/06/02 20:03:09 rillig Exp $ -->
2 2
3<chapter id="bulk"> 3<chapter id="bulk">
4<title>Creating binary packages for everything in pkgsrc (bulk 4<title>Creating binary packages for everything in pkgsrc (bulk
5builds)</title> 5builds)</title>
6 6
7<para>For a number of reasons, you may want to build binary packages 7<para>For a number of reasons, you may want to build binary packages
8for a large selected set of packages in pkgsrc, or even for all pkgsrc packages. 8for a large selected set of packages in pkgsrc, or even for all pkgsrc packages.
9For instance, when you have multiple machines that should run the same software, 9For instance, when you have multiple machines that should run the same software,
10it is wasted time if they all build their packages themselves from source. 10it is wasted time if they all build their packages themselves from source.
11Or you may want to build a list of packages you want and check them before 11Or you may want to build a list of packages you want and check them before
12deploying onto production systems. 12deploying onto production systems.
13There is a way of getting a set of binary packages: 13There is a way of getting a set of binary packages:
14the bulk build system, or pbulk ("p" stands for "parallel"). 14the bulk build system, or pbulk ("p" stands for "parallel").
@@ -64,29 +64,29 @@ are. @@ -64,29 +64,29 @@ are.
64 64
65<listitem><para>The packages must be built as root, since some packages 65<listitem><para>The packages must be built as root, since some packages
66require set-uid binaries at runtime, and creating those packages as 66require set-uid binaries at runtime, and creating those packages as
67unprivileged user doesn't work well at the moment.</para></listitem> 67unprivileged user doesn't work well at the moment.</para></listitem>
68 68
69</itemizedlist> 69</itemizedlist>
70</listitem> 70</listitem>
71 71
72</itemizedlist> 72</itemizedlist>
73--> 73-->
74</sect1> 74</sect1>
75 75
76<sect1 id="bulk.pbulk"> 76<sect1 id="bulk.pbulk">
77<title>Running a pbulk-style bulk build</title> 77<title>Running a bulk build</title>
78 78
79<para>Running a pbulk-style bulk build works roughly as follows:</para> 79<para>Running a bulk build works roughly as follows:</para>
80 80
81<itemizedlist> 81<itemizedlist>
82<listitem><para>First, build the pbulk infrastructure in a fresh pkgsrc location.</para></listitem> 82<listitem><para>First, build the pbulk infrastructure in a fresh pkgsrc location.</para></listitem>
83<listitem><para>Then, build each of the packages from a clean installation directory using the infrastructure.</para></listitem> 83<listitem><para>Then, build each of the packages from a clean installation directory using the infrastructure.</para></listitem>
84</itemizedlist> 84</itemizedlist>
85 85
86<sect2 id="bulk.pbulk.conf"> 86<sect2 id="bulk.pbulk.conf">
87<title>Configuration</title> 87<title>Configuration</title>
88 88
89<para>To simplify configuration, we provide the helper script <filename>mk/pbulk/pbulk.sh</filename>.</para> 89<para>To simplify configuration, we provide the helper script <filename>mk/pbulk/pbulk.sh</filename>.</para>
90 90
91<para>In order to use it, prepare a clear system (real one, chroot environment, jail, zone, virtual machine). 91<para>In order to use it, prepare a clear system (real one, chroot environment, jail, zone, virtual machine).
92Configure network access to fetch distribution files. 92Configure network access to fetch distribution files.