[pkgsrc/trunk]: pkgsrc 3.2.6 Setting up a sandbox for chroot'ed builds:

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

details:   https://anonhg.NetBSD.org/pkgsrc/rev/699d5e33b154
branches:  trunk
changeset: 463601:699d5e33b154
user:      hubertf <hubertf%pkgsrc.org@localhost>
date:      Wed Nov 19 22:31:47 2003 +0000

description:
3.2.6 Setting up a sandbox for chroot'ed builds:
Remove redundant paragraphs, and remind creating a user account if
$CVS_USER is set in build.conf. (We should probably check for a few
things there...)

diffstat:

 Packages.txt |  32 +++++++++++++-------------------
 1 files changed, 13 insertions(+), 19 deletions(-)

diffs (56 lines):

diff -r 8ec245fd9432 -r 699d5e33b154 Packages.txt
--- a/Packages.txt      Wed Nov 19 16:16:47 2003 +0000
+++ b/Packages.txt      Wed Nov 19 22:31:47 2003 +0000
@@ -1,4 +1,4 @@
-# $NetBSD: Packages.txt,v 1.318 2003/11/12 21:16:39 wiz Exp $
+# $NetBSD: Packages.txt,v 1.319 2003/11/19 22:31:47 hubertf Exp $
 ###########################################################################
 
                        ==========================
@@ -524,11 +524,14 @@
 bulk build inside a chroot environment.
 
 The first step to do so is setting up a chroot sandbox, e.g. /usr/sandbox.
-After extracting all the sets from a NetBSD installation or doing a
-"make distribution DESTDIR=/usr/sandbox" in src/etc, make sure the following
-items are present and properly configured:
-
- * kernel:
+Extract all sets from a NetBSD installation or doing a "make distribution
+DESTDIR=/usr/sandbox" in src/etc, also don't forget to install X - if you
+are a developer and want to upload the resulting binary packages to
+ftp.netbsd.org, make sure you are using the default X version for your
+architecture and release (up to 1.6, that is 3.3.6 for all architectures).
+Then, make sure the following items are present and properly configured:
+
+ * Kernel:
    cp /netbsd /usr/sandbox
  * /dev/*:
    cd /usr/sandbox/dev ; sh MAKEDEV all
@@ -548,22 +551,13 @@
    mkdir /usr/sandbox/usr/pkg
  * checkout pkgsrc from cvs, into /usr/sandbox/usr/pkgsrc
    cvs -d cvs.netbsd.org:/cvsroot co pkgsrc
+   Do not mount/link this to the copy of your pkgsrc tree you do
+   development in, as this will likely cause problems! 
  * /usr/pkgsrc/packages & .../distfiles (point outside of sandbox)
  * /etc/mk.conf, see 3.2.1.1
  * adjust .../mk/bulk/build.conf
-
-!!! Don't forget to install X !!!
-If you are a developer and want to upload the resulting binary packages
-to ftp.netbsd.org, make sure you are using the default X version for your
-architecture and release (up to 1.6, that is 3.3.6 for all architectures).
-
-Next thing you will want to is make sure /usr/sandbox/usr/pkgsrc contains a
-fresh checkout of pkgsrc (e.g. from anoncvs). Do not mount/link this to the
-copy of your pkgsrc tree you do development in, as this will likely cause
-problems! Adjust .../pkgsrc/packages and .../pkgsrc/distfiles to point to
-some places outside the sandbox if you want to make the files public.
-
-Then, configure .../pkgsrc/mk/bulk/build.conf to fit your needs!
+ * If you have set CVS_USER in build.conf, make sure that account exists
+   and can do a "cvs ${CVS_FLAGS} update" properly!
 
 When the chroot sandbox is setup, you can start the build with the following
 steps: