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
53 trees. For this purpose, a script
54 .Pq Pa src/release/generate-release.sh
55 is provided to automate these checkouts and then execute
60 Before attempting to build a release, the user is expected to be
61 familiar with the contents of
63 and should have experience upgrading systems from source.
65 The release build process requires that
67 be populated with the output of
68 .Dq Li "make buildworld"
70 .Dq Li "make buildkernel" .
71 This is necessary to provide the object files for the release or, when
73 .Pa generate-release.sh ,
74 so that the object files for a complete system can be installed into a clean
76 environment. In this second case, the built world must be capable of running
77 on the build system (i.e. it must be for the same architecture and be
78 compatible with the installed kernel).
79 The release procedure on some architectures may also require that the
81 (memory disk) device driver be present in the kernel
82 (either by being compiled in or available as a module).
84 This document does not cover source code management, quality
85 assurance, or other aspects of the release engineering process.
86 .Sh CLEAN RELEASE GENERATION
87 Official releases of FreeBSD are produced in a totally clean environment to
88 ensure consistency between the versions of the src, ports, and doc trees
89 and to avoid contamination from the host system (e.g. local patches, changes
92 etc.). This is accomplished using the wrapper script
93 .Pa src/release/generate-release.sh .
95 .Ic generate-release.sh
96 svn-branch scratch-dir
98 .Ic generate-release.sh
100 .Dq Li "make installworld"
105 It then checks out the src tree specified by
109 and (optionally) the ports and documentation trees using
113 Once the various source trees have been obtained, it executes
114 .Dq Li "make release"
117 environment and places the result in
119 Note that because this uses a chroot, it cannot be used to cross-build
123 Environment variables:
124 .Bl -tag -width ".Cm MAKE_FLAGS"
126 The CVSUP server to use for the doc and ports trees. One of
130 must be specified for ports and documentation to be included in the release.
134 CVS repository to use for the doc and ports trees. One of
138 must be specified for ports and documentation to be included in the release.
142 is set, that tag will be used for CVS checkouts (doc and ports), otherwise
143 .Ic generate-release.sh
146 This environment variable can be set to pass flags (e.g. -j) to
148 when invoked by the script.
150 The location of the FreeBSD SVN source repository. Defaults to
151 .Pa svn://svn.freebsd.org/base .
155 .Pq Pa src/release/Makefile
157 Most developers will only be concerned with the
162 .\" XXX: Some sort of introduction to this list? All the others have one.
163 .Bl -tag -width ".Cm packagesystem"
165 Meta-target to build all release media and distributions applicable to this
168 Copy all produced release media to
171 Builds installation CD-ROM images. On some systems, this may require that
174 .Pq Pa sysutils/cdrtools
175 and possibly that the
177 (memory disk) device driver be present in the kernel
178 (either by being compiled in or available as a module). This target
179 produces files called
185 Builds an installation memory stick image named
187 Not applicable on all platforms. Requires that the
189 (memory disk) device driver be present in the kernel
190 (either by being compiled in or available as a module).
192 Creates a directory named
194 containing the distribution files used in network installations
195 and suitable for upload to an FTP mirror.
198 Major subtargets called by targets above:
199 .Bl -tag -width ".Cm packagesystem"
201 Generates all the distribution archives (e.g. base, kernel, ports, doc)
202 applicable on this platform.
204 Builds a bootable installation system containing all the distribution files
207 target, and suitable for imaging by the
213 Builds the release documentation.
214 This includes the release notes,
215 hardware guide, and installation instructions. Other documentation (e.g.
216 the Handbook) is built during the
223 .Bl -tag -width ".Va TARGET_ARCH"
225 Location of a directory containing the src tree. By default, the directory
226 above the one containing the makefile
229 Location of a directory containing the ports tree. By default,
231 If it is unset or cannot be found, ports will not be included in the release.
233 Location of a directory containing the doc tree. By default,
235 If it is unset or cannot be found, most documentation will not be included in
240 If defined, the Ports Collection will be omitted from the release.
242 If set, do not include system source code in the release.
244 If defined, the SGML-based documentation from the
246 Documentation Project will not be built.
249 distribution will still be created with the minimal documentation set
253 The target hardware platform.
254 This is analogous to the
257 This is necessary to cross-build some target architectures.
258 For example, cross-building for PC98 machines requires
259 .Va TARGET_ARCH Ns = Ns Li i386
261 .Va TARGET Ns = Ns Li pc98 .
264 defaults to the current hardware platform.
266 The target machine processor architecture.
267 This is analogous to the
270 Set this to cross-build for a different architecture.
273 defaults to the current machine architecture, unless
275 is also set, in which case it defaults to the appropriate
276 value for that platform.
277 Typically, one only needs to set
282 .It Pa /usr/doc/Makefile
283 .It Pa /usr/doc/share/mk/doc.project.mk
284 .It Pa /usr/ports/Mk/bsd.port.mk
285 .It Pa /usr/ports/Mk/bsd.sites.mk
286 .It Pa /usr/share/examples/etc/make.conf
287 .It Pa /usr/src/Makefile
288 .It Pa /usr/src/Makefile.inc1
289 .It Pa /usr/src/release/Makefile
290 .It Pa /usr/src/release/generate-release.sh
293 The following sequence of commands can be used to build a
294 .Dq "-CURRENT snapshot":
295 .Bd -literal -offset indent
297 svn co svn://svn.freebsd.org/base/head src
299 make buildworld buildkernel
302 make install DESTDIR=/var/freebsd-snapshot
305 After running these commands, all produced distribution files (tarballs
306 for FTP, CD-ROM images, etc.) are available in the
307 .Pa /var/freebsd-snapshot
310 The following sequence of commands can be used to build a
311 .Dq "-CURRENT snapshot"
312 in a clean environment, including ports and documentation:
313 .Bd -literal -offset indent
317 export CVSUP_HOST=cvsupN.freebsd.org
318 sh generate-release.sh head /local3/release
321 After running these commands, all prepared release files are available in the
322 .Pa /local3/release/R
329 .Xr svn 1 Pq Pa ports/devel/subversion-freebsd ,
339 .%T "FreeBSD Release Engineering"
340 .%U http://www.FreeBSD.org/doc/en_US.ISO8859-1/articles/releng/
343 .%T "FreeBSD Release Engineering of Third Party Packages"
344 .%U http://www.FreeBSD.org/doc/en_US.ISO8859-1/articles/releng-packages/
347 .%T "FreeBSD Developers' Handbook"
348 .%U http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/developers-handbook/
353 used a manual checklist, compiled by
355 to produce a release.
356 Apart from being incomplete, the list put a lot of specific demands on
357 available file systems and was quite torturous to execute.
361 release engineering effort, significant
362 effort was spent getting
363 .Pa src/release/Makefile
364 into a shape where it could at least automate most of the tediousness
365 of building a release in a sterile environment.
370 .Pa src/release/Makefile
371 was overhauled and the wrapper script
372 .Pa src/release/generate-release.sh
373 introduced to support the introduction of a new installer.
375 At near 1000 revisions spread over multiple branches, the
378 .Pa src/release/Makefile
379 contains a vivid historical record of some
380 of the hardships release engineers go through.
382 .Pa src/release/Makefile
383 was originally written by
388 .An Poul-Henning Kamp .
389 This manual page was written by
390 .An Murray Stokely Aq murray@FreeBSD.org .