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
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
41 source code repository in
43 A complete release can actually be built with only a single command,
44 including the creation of ISO images suitable for burning to CD-ROM,
45 memory stick images, and an FTP install directory.
46 This command is aptly named
47 .Dq Li "make release" .
49 For some users, it may be desirable to provide an absolutely clean
50 build environment, with no local modifications to the source tree or to
52 and with clean checkouts of specific versions of the doc, src, and ports
54 For this purpose, a script
55 .Pq Pa src/release/release.sh
56 is provided to automate these checkouts and then execute
61 Before attempting to build a release, the user is expected to be
62 familiar with the contents of
64 and should have experience upgrading systems from source.
66 The release build process requires that
68 be populated with the output of
69 .Dq Li "make buildworld"
71 .Dq Li "make buildkernel" .
72 This is necessary to provide the object files for the release or, when
75 so that the object files for a complete system can be installed into a clean
79 If the target release build is for a different architecture or machine type,
84 variables must be used.
87 variables for more information.
89 The release procedure on some architectures may also require that the
91 (memory disk) device driver be present in the kernel
92 .Pq either by being compiled in or available as a module .
94 This document does not cover source code management, quality
95 assurance, or other aspects of the release engineering process.
96 .Sh CLEAN RELEASE GENERATION
99 are produced in a totally clean environment to
100 ensure consistency between the versions of the src, ports, and doc trees
101 and to avoid contamination from the host system
102 .Po such as local patches, changes
107 This is accomplished using the wrapper script
108 .Pa src/release/release.sh .
111 .Op Fl c Ar release.conf
122 .Dq Li "make buildworld"
124 .Dq Li "make installworld"
129 .Dq Li "make release"
132 environment and places the result in
137 configuration file supports the following variables:
140 The directory within which the release will be built.
144 host used to check out the various trees.
146 .Pa svn://svn.FreeeBSD.org .
166 The target machine type for cross-building a release.
168 The target machine architecture for cross-building a release.
170 For the supported list of
174 combinations, consult the output of
179 The target kernel configuration to use.
184 entries may be specified.
188 to use for the release build.
191 to prevent polluting the release with local system changes.
195 to use for the release build.
198 to prevent polluting the release with local system changes.
200 Additional flags to pass to
203 Additional flags to pass to
208 Defaults to setting the number of
212 to the number of CPUs available on a SMP-capable system.
214 Additional flags to pass to
219 Defaults to setting the number of
223 to half the number of CPUs available on a SMP-capable system.
225 Set to a non-empty value to skip the
232 distribution package from being created.
234 Set to a non-empty value to skip the
241 distribution package from being created.
242 Setting this also sets
245 Set to a non-empty value to include the
251 .Pq Pa src/release/Makefile
253 Most developers will only be concerned with the
258 .\" XXX: Some sort of introduction to this list? All the others have one.
259 .Bl -tag -width ".Cm packagesystem"
261 Meta-target to build all release media and distributions applicable to this
264 Copy all produced release media to
267 Builds installation CD-ROM images.
270 (memory disk) device driver be present in the kernel
271 (either by being compiled in or available as a module).
272 This target produces files called
278 Builds installation DVD-ROM images.
281 (memory disk) device driver be present in the kernel
282 (either by being compiled in or available as a module).
283 This target produces the
287 Builds an installation memory stick image named
289 Not applicable on all platforms.
293 device driver be present in the kernel
294 .Pq either by being compiled in or available as a module .
298 with the exception that the installation distribution sets
301 Creates a directory named
303 containing the distribution files used in network installations
304 and suitable for upload to an FTP mirror.
307 Major subtargets called by targets above:
308 .Bl -tag -width ".Cm packagesystem"
310 Generates all the distribution archives
311 .Pq base, kernel, ports, doc
312 applicable on this platform.
314 Builds a bootable installation system containing all the distribution files
317 target, and suitable for imaging by the
324 Builds the release documentation.
325 This includes the release notes,
326 hardware guide, and installation instructions.
327 Other documentation, such as the Handbook,
335 .Bl -tag -width ".Ev TARGET_ARCH"
337 Optional base name for generated media images
338 .Pq e.g., FreeBSD-9.0-RC2-amd64 .
339 Defaults to the output of
340 .Ic `uname -s`-`uname -r`-`uname -p`
343 Location of a directory containing the src tree.
344 By default, the directory
345 above the one containing the makefile
348 Location of a directory containing the ports tree.
351 If it is unset or cannot be found, ports will not be included in the release.
353 Location of a directory containing the doc tree.
356 If it is unset or cannot be found, most documentation will not be included in
361 If defined, the Ports Collection will be omitted from the release.
363 If set, do not include system source code in the release.
365 If defined, the XML-based documentation from the
367 Documentation Project will not be built.
370 distribution will still be created with the minimal documentation set
374 The target hardware platform.
375 This is analogous to the
378 This is necessary to cross-build some target architectures.
379 For example, cross-building for PC98 machines requires
380 .Ev TARGET_ARCH Ns = Ns Li i386
382 .Ev TARGET Ns = Ns Li pc98 .
385 defaults to the current hardware platform.
387 The target machine processor architecture.
388 This is analogous to the
391 Set this to cross-build for a different architecture.
394 defaults to the current machine architecture, unless
396 is also set, in which case it defaults to the appropriate
397 value for that platform.
398 Typically, one only needs to set
402 .Bl -tag -compact -width Pa
403 .It Pa /usr/doc/Makefile
404 .It Pa /usr/doc/share/mk/doc.project.mk
405 .It Pa /usr/ports/Mk/bsd.port.mk
406 .It Pa /usr/ports/Mk/bsd.sites.mk
407 .It Pa /usr/share/examples/etc/make.conf
408 .It Pa /usr/src/Makefile
409 .It Pa /usr/src/Makefile.inc1
410 .It Pa /usr/src/release/Makefile
411 .It Pa /usr/src/release/release.sh
412 .It Pa /usr/src/release/release.conf.sample
415 The following sequence of commands can be used to build a
416 .Dq "-CURRENT snapshot":
417 .Bd -literal -offset indent
419 svn co svn://svn.freebsd.org/base/head src
421 make buildworld buildkernel
424 make install DESTDIR=/var/freebsd-snapshot
427 After running these commands, all produced distribution files (tarballs
428 for FTP, CD-ROM images, etc.) are available in the
429 .Pa /var/freebsd-snapshot
432 The following sequence of commands can be used to build a
433 .Dq "-CURRENT snapshot"
434 in a clean environment, including ports and documentation:
435 .Bd -literal -offset indent
440 Optionally, a configuration file can be used customize the release build,
441 such as the subversion revision to use, the branch of the subversion tree for
446 .Bd -literal -offset indent
448 sh release.sh -c $HOME/release.conf
451 After running these commands, all prepared release files are available in the
454 The target directory can be changed by specifying the
462 .Xr svn 1 Pq Pa ports/devel/subversion ,
472 .%T "FreeBSD Release Engineering"
473 .%U http://www.FreeBSD.org/doc/en_US.ISO8859-1/articles/releng/
476 .%T "FreeBSD Release Engineering of Third Party Packages"
477 .%U http://www.FreeBSD.org/doc/en_US.ISO8859-1/articles/releng-packages/
480 .%T "FreeBSD Developers' Handbook"
481 .%U http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/developers-handbook/
486 used a manual checklist, compiled by
488 to produce a release.
489 Apart from being incomplete, the list put a lot of specific demands on
490 available file systems and was quite torturous to execute.
494 release engineering effort, significant
495 effort was spent getting
496 .Pa src/release/Makefile
497 into a shape where it could at least automate most of the tediousness
498 of building a release in a sterile environment.
503 .Pa src/release/Makefile
504 was overhauled and the wrapper script
505 .Pa src/release/generate-release.sh
506 introduced to support the introduction of a new installer.
511 .Pa src/release/release.sh
512 was introduced to support per-build configuration files.
513 .Pa src/release/release.sh
514 is heavily based on the
515 .Pa src/release/generate-release.sh
518 At near 1000 revisions spread over multiple branches, the
521 .Pa src/release/Makefile
522 contains a vivid historical record of some
523 of the hardships release engineers go through.
525 .Pa src/release/Makefile
526 was originally written by
531 .An Poul-Henning Kamp .
533 This manual page was originally written by
534 .An Murray Stokely Aq murray@FreeBSD.org .
537 .An Nathan Whitehorn Aq nwhitehorn@FreeBSD.org
539 .Fa generate-release.sh
544 It was later updated by
545 .An Glen Barber Aq gjb@FreeBSD.org