From 6d11e7c4ba4283a8ddfc86fd8cdb29bfecb6da33 Mon Sep 17 00:00:00 2001 From: Murray Stokely Date: Wed, 13 Feb 2002 10:34:51 +0000 Subject: [PATCH] Correct a few typos. Add a few paragraphs from the Handbook to describe how to mirror a local CVS repository, and point to the CVSup section of the Handbook for more details. Note that if RELEASETAG is omitted from "make release", then a -CURRENT snapshot will be built. (Also from Handbook). --- en_US.ISO8859-1/articles/releng/article.sgml | 31 ++++++++++++++------ 1 file changed, 22 insertions(+), 9 deletions(-) diff --git a/en_US.ISO8859-1/articles/releng/article.sgml b/en_US.ISO8859-1/articles/releng/article.sgml index 73860d8935..c0f1421e0a 100644 --- a/en_US.ISO8859-1/articles/releng/article.sgml +++ b/en_US.ISO8859-1/articles/releng/article.sgml @@ -129,7 +129,7 @@ Section 2 discusses the different phases of the release engineering process leading up to the actual system build and section - 3 descibes the actual build process. describes the actual build process. Section 4 describes how the base release may be extended by third parties and section 5 details some of the @@ -377,19 +377,19 @@ FreeBSD releases can be built by anyone with a fast machine and access to a source repository. (That should be everyone, since we offer anonymous CVS! See The Handbook for - details.). The only special requirement is + details.). The only special requirement is that the vn (On -CURRENT, this device has been replaced by the new md memory disk driver .) device must be available. If the device is not loaded into your kernel, then the kernel module should be automatically loaded when &man.vnconfig.8; is executed - during the boot media creation phase. All of the tools necessary + during the boot media creation phase. All of the tools necessary to build a release are available from the CVS repository in - src/release. These tools aim to provide a - consistent way to build FreeBSD releases. A complete release can + src/release. These tools aim to provide a + consistent way to build FreeBSD releases. A complete release can actually be built with only a single command, including the creation of ISO images suitable for burning to - CDROM, installation floppies, and an FTP install directory. This + CDROM, installation floppies, and an FTP install directory. This command is aptly named make release. @@ -426,6 +426,19 @@ + If you do not already have access to a local CVS + repository, then you may mirror one with CVSup. + The supplied supfile, + /usr/share/examples/cvsup/cvs-supfile, is + a useful starting point for mirroring the CVS + repository. + + If RELEASETAG is omitted, then the + release will be built from the HEAD (a.k.a. -CURRENT) branch. + Releases built from this branch are normally referred to as + -CURRENT snapshots. + There are many other variables available to customize the release build. Most of these variables are documented at the top of src/release/Makefile. The exact @@ -438,9 +451,9 @@ RELEASETAG=RELENG_4_4_0_RELEASE - + The release Makefile can be broken down into several distinct - steps. + steps. @@ -828,7 +841,7 @@ - + Acknowledgements