1 .\" Copyright (c) 2002 Murray Stokely <murray@FreeBSD.org>
2 .\" All rights reserved.
4 .\" Redistribution and use in source and binary forms, with or without
5 .\" modification, are permitted provided that the following conditions
7 .\" 1. Redistributions of source code must retain the above copyright
8 .\" notice, this list of conditions and the following disclaimer.
9 .\" 2. Redistributions in binary form must reproduce the above copyright
10 .\" notice, this list of conditions and the following disclaimer in the
11 .\" documentation and/or other materials provided with the distribution.
13 .\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND
14 .\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
15 .\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
16 .\" ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR BE LIABLE
17 .\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
18 .\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
19 .\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
20 .\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
21 .\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
22 .\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
25 .\" $FreeBSD: src/share/man/man7/release.7,v 1.3.2.6 2003/04/12 20:42:30 murray Exp $
32 .Nd "release building infrastructure"
35 provides a complete build environment suitable for users to make
39 All of the tools necessary to build a release are available from the
42 A complete release can actually be built with only a single command,
43 including the creation of ISO images suitable for burning to CD-ROM,
44 installation floppies, and an FTP install directory.
45 This command is aptly named
46 .Dq Li "make release" .
48 Before attempting to build a release, the user is expected to be
49 familiar with the contents of
51 and should have experience upgrading systems from source with
53 The release build process requires that
55 be populated with the output of
56 .Dq Li "make buildworld" .
57 This is necessary so that the object files for a complete system can
58 be installed into a clean
61 The release procedure also requires that the
63 (vnode disk) device driver be present in the kernel
64 (either by being compiled in or loaded as a module).
66 This document does not cover source code management, quality
67 assurance, or other aspects of the release engineering process.
70 .Pq Pa src/release/Makefile
72 Most developers will only be concerned with the
75 .\" XXX: Some sort of introduction to this list? All the others have one.
76 .Bl -tag -width ".Cm rerelease"
79 .Dq Li "make installworld"
80 to install a clean system into a
82 environment on the filesystem.
83 Checks out the specified version of the source code and then rebuilds
84 the entire system in the clean environment with
86 The detailed steps that follow are then executed to package up the
87 different distributions, build the installation floppy disks, build
88 release documentation, and so on.
90 This target must be built as root with the
95 Assumes that the output of a release build has been manually modified,
96 and performs the minimal number of steps to rebuild the release using
97 the intermediate output of the previous
98 .Dq Li "make release" .
100 Generate a new set of boot floppies.
106 targets to re-generate the floppy images of a previous
107 .Dq Li "make release" .
108 This is most often used to build custom boot floppies.
112 .Dq Li "make release" :
113 .Bl -tag -width ".Cm release.10"
119 to build the directory hierarchy for the system.
121 Installs the system into the distribution directories.
130 .\" XXX: We build more than one kernel. We build a stripped down
131 .\" kernel for the boot media in addition to a full GENERIC kernel.
132 Makes and installs the
140 binaries to live on the installation floppies.
142 Builds synthetic distributions, and cleans up the previously built
145 Creates tarballs of the assembled distribution trees.
147 Makes source distributions.
149 Creates the boot and MFS root floppies.
151 Creates the fixit floppy.
153 Sets up a suitable area for FTP installations in
154 .Pa ${CHROOTDIR}/R/ftp .
156 Sets up a suitable area to build CD-ROM images in
157 .Pa ${CHROOTDIR}/R/cdrom .
159 Builds two ISO images (installation and
161 filesystem) from the CD-ROM release area
162 (disabled by default, see
166 Builds all of the necessary tools to turn the
168 Documentation Project source documents (SGML, XML) into HTML
169 and text documents that will accompany the release.
170 Also, builds and installs the actual user documentation.
171 This includes the Handbook, FAQ, articles, and so on.
173 Builds the release documentation.
174 This includes the release notes,
175 hardware guide, and installation instructions.
178 Variables that must be specified:
179 .Bl -tag -width ".Va RELEASETAG"
181 The directory to be used as the
183 environment for the entire release build.
184 .\" XXX: I recommend against hardcoding specific numbers like "2.3" here;
185 .\" XXX: perhaps it should be replaced with something to the effect of
186 .\" XXX: "we don't know how much space you'll need, but make sure you have
187 .\" XXX: at least 3 GB to be safe" (I know i'm still hardcoding a number,
188 .\" XXX: but at least it looks less like a decree and more like an estimate.
189 This filesystem should have at least 2.3 gigabytes of free space on the
192 The name of the release to be built.
193 This is used to set the
196 .Pa sys/conf/newvers.sh ,
197 which affects the output of
203 This path name is referenced to the real system root,
209 The CVS tag corresponding to the release that is to be built.
210 If undefined, the release will be built from the
214 .Dq "-CURRENT snapshot" ) .
218 .Bl -tag -width ".Va RELEASEDISTFILES"
220 Additional arguments for
226 For example, setting this variable to
227 .Dq Li "-D '01/01/2002 00:00:00 GMT'"
229 .Dq Li "make release"
231 .Dq Li "make rerelease"
234 to check out or update sources as of 00:00:00 GMT, January 1 2002, respectively.
238 that will be applied in the
240 environment before the release build begins.
244 command used to apply
248 A script that will be run in the
250 environment immediately after any local patches are applied.
252 If defined, bootable ISO CD-ROM images will be created from the
253 contents of the CD-ROM stage directory.
257 the SGML-based documentation from the
259 Documentation Project will not be built.
262 distribution will still be created with the minimal documentation set
268 then the Ports Collection will be omitted from the release.
270 If defined, readme files will not be created for each individual port
271 in the Ports Collection.
272 The default behavior is for
273 .Dq Li "make release"
275 .Dq Li "make readmes"
277 .Pa ${CHROOTDIR}/usr/ports ,
278 which can be a very time consuming operation.
279 .It Va RELEASEDISTFILES
280 The directory where the distribution files for ports required by the
281 release build can be found.
282 This may save a significant amount of time over downloading the
283 distfiles through a slow link.
284 .It Va RELEASENOUPDATE
285 If this variable is defined for
286 .Dq Li "make rerelease" ,
287 the source code will not be updated with
288 .Dq Li "cvs update" .
290 The target machine processor architecture.
291 This is analogous to the
294 Set this to cross-build for a different architecture.
296 The target hardware platform.
297 This is analogous to the
300 This is necessary to cross-build some target architectures.
301 For example, cross-building for PC98 machines requires
302 .Va TARGET_ARCH Ns = Ns Li i386
304 .Va TARGET Ns = Ns Li pc98 .
308 .It Pa /etc/make.conf
309 .It Pa /usr/doc/Makefile
310 .It Pa /usr/doc/share/mk/doc.project.mk
311 .It Pa /usr/ports/Mk/bsd.port.mk
312 .It Pa /usr/ports/Mk/bsd.sites.mk
313 .It Pa /usr/share/examples/etc/make.conf
314 .It Pa /usr/src/Makefile
315 .It Pa /usr/src/Makefile.inc1
316 .It Pa /usr/src/release/Makefile
317 .It Pa /usr/src/release/${arch}/drivers.conf
318 .It Pa /usr/src/release/${arch}/boot_crunch.conf
319 .It Pa /usr/src/release/${arch}/fixit_crunch.conf
322 The following sequence of commands was used to build the
325 .Bd -literal -offset indent
327 cvs co -rRELENG_4_5_0_RELEASE src
331 make release CHROOTDIR=/local3/release BUILDNAME=4.5-RELEASE \\
332 CVSROOT=/host/cvs/usr/home/ncvs RELEASETAG=RELENG_4_5_0_RELEASE
335 After running these commands, a complete system suitable for FTP or
336 CD-ROM distribution is available in the
337 .Pa /local3/release/R
340 The following sequence of commands can be used to build a
341 .Dq "-CURRENT snapshot"
343 locally modified source tree:
344 .Bd -literal -offset indent
346 cvs diff -u > /path/to/local.patch
349 make release CHROOTDIR=/local3/release BUILDNAME=5.0-CURRENT \\
350 CVSROOT=/host/cvs/usr/home/ncvs LOCAL_PATCHES=/path/to/local.patch
369 .%T "FreeBSD Release Engineering"
370 .%O http://www.FreeBSD.org/doc/en_US.ISO8859-1/articles/releng/
373 .%T "FreeBSD Release Engineering of Third Party Packages"
374 .%O http://www.FreeBSD.org/doc/en_US.ISO8859-1/articles/releng-packages/
377 .%T "FreeBSD Developers' Handbook"
378 .%O http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/developers-handbook/
383 used a manual checklist, compiled by
385 to produce a release.
386 Apart from being incomplete, the list put a lot of specific demands on
387 available filesystems and was quite torturous to execute.
391 release engineering effort, significant
392 effort was spent getting
393 .Pa src/release/Makefile
394 into a shape where it could at least automate most of the tediousness
395 of building a release in a sterile environment.
397 With its almost 1000 revisions spread over multiple branches, the
400 .Pa src/release/Makefile
401 contains a vivid historical record of some
402 of the hardships release engineers go through.
404 .Pa src/release/Makefile
405 was originally written by
410 .An Poul-Henning Kamp .
411 This manual page was written by
412 .An Murray Stokely Aq murray@FreeBSD.org .
414 Infrastructure changes are occassionally made to the FreeBSD
415 documentation set in such a way that release builds on security
417 To work around this, release builds can be made to checkout the
418 documentation from the last fully supported release of FreeBSD.
420 .Bd -literal -offset indent
421 make release RELEASETAG=RELENG_4_5 DOCRELEASETAG=RELEASE_4_5_0 ...