[pkgsrc/trunk]: pkgsrc/doc/guide/files bulk.xml: add a bulk build link, and t...

[gutteridge <gutteridge%pkgsrc.org@localhost>]

details:   https://anonhg.NetBSD.org/pkgsrc/rev/54d1a71ee14c
branches:  trunk
changeset: 430303:54d1a71ee14c
user:      gutteridge <gutteridge%pkgsrc.org@localhost>
date:      Wed Apr 29 23:20:42 2020 +0000

description:
bulk.xml: add a bulk build link, and tidy up grammar

Add a link to bulk build resource requirement estimates, and, while
here, fix some grammatical issues.

diffstat:

 doc/guide/files/bulk.xml |  20 ++++++++++----------
 1 files changed, 10 insertions(+), 10 deletions(-)

diffs (50 lines):

diff -r 8e70c1340e6a -r 54d1a71ee14c doc/guide/files/bulk.xml
--- a/doc/guide/files/bulk.xml  Wed Apr 29 23:15:15 2020 +0000
+++ b/doc/guide/files/bulk.xml  Wed Apr 29 23:20:42 2020 +0000
@@ -1,17 +1,17 @@
-<!-- $NetBSD: bulk.xml,v 1.26 2019/04/03 14:41:24 sevan Exp $ -->
+<!-- $NetBSD: bulk.xml,v 1.27 2020/04/29 23:20:42 gutteridge Exp $ -->
 
 <chapter id="bulk">
 <title>Creating binary packages for everything in pkgsrc (bulk
 builds)</title>
 
-<para>For a number of reasons you may want to build binary packages
-for a large selected set of packages in pkgsrc or even for all pkgsrc packages.
+<para>For a number of reasons, you may want to build binary packages
+for a large selected set of packages in pkgsrc, or even for all pkgsrc packages.
 For instance, when you have multiple machines that should run the same software,
 it is wasted time if they all build their packages themselves from source.
 Or you may want to build a list of packages you want and check them before
-deploying onto production system.
+deploying onto production systems.
 There is a way of getting a set of binary packages:
-The bulk build system, or pbulk ("p" stands for "parallel").
+the bulk build system, or pbulk ("p" stands for "parallel").
 This chapter describes how to set it up.</para>
 
 <sect1 id="bulk.pre">
@@ -20,10 +20,10 @@
 <para>First of all, you have to decide whether you build all packages
 or a limited set of them. Full bulk builds usually consume a lot more resources,
 both space and time, than builds for some practical sets of packages.
-There exists a number of particularly heavy packages that are not actually
-interesting to a wide audience.
-<!-- approximate resource consumption for full bulk build is given in section <put a reference here/> -->
-For a limited bulk builds you need to make a list of packages you want to build.
+A number of particularly heavy packages exist that are not actually
+interesting to a wide audience. (The approximate resource consumption for a
+full bulk build is given in section <xref linkend="bulk.req" />.)
+For limited bulk builds you need to make a list of packages you want to build.
 Note that all their dependencies will be built, so you don't need to track them manually.
 </para>
 
@@ -221,7 +221,7 @@
       <para>If you wish to include a common set of files
       (<filename>COPYRIGHT</filename>, <filename>README</filename>,
       etc.) on each CD in the collection, then you need to create a
-      directory which contains these files. e.g.</para>
+      directory which contains these files, e.g.:</para>
 
       <screen>
 &rprompt; <userinput>mkdir /tmp/common</userinput>