The translation is temporarily closed for contributions due to maintenance, please come back later.

Source string Read only

(itstool) path: sect2/para
Context English State
<filename>share/images/articles/releng/branches-releng<replaceable>X</replaceable>.pic</filename>
<filename>head/share/xml/release.ent</filename>
<filename>en_US.ISO8859-1/htdocs/releases/*</filename>
<filename>en_US.ISO8859-1/htdocs/releng/index.xml</filename>
<filename>share/xml/news.xml</filename>
Additionally, update the <quote>BSD Family Tree</quote> file:
<filename>src/share/misc/bsd-family-tree</filename>
Creating the Release Tag
When the final release is ready, the following command will create the <literal>release/9.2.0</literal> tag.
<prompt>#</prompt> <userinput>svn cp $FSVN/releng/9.2 $FSVN/release/9.2.0</userinput>
The Documentation and Ports managers are responsible for tagging their respective trees with the <literal>tags/RELEASE_9_2_0</literal> tag.
When the Subversion <command>svn cp</command> command is used to create a <emphasis>release tag</emphasis>, this identifies the source at a specific point in time. By creating tags, we ensure that future release builders will always be able to use the exact same source we used to create the official FreeBSD Project releases.
Release Building
FreeBSD <quote>releases</quote> can be built by anyone with a fast machine and access to a source repository. (That should be everyone, since we offer Subversion access! See the <link xlink:href="@@URL_RELPREFIX@@/doc/en_US.ISO8859-1/books/handbook/svn.html">Subversion section in the Handbook</link> for details.) The <emphasis>only</emphasis> special requirement is that the <citerefentry><refentrytitle>md</refentrytitle><manvolnum>4</manvolnum></citerefentry> device must be available. If the device is not loaded into your kernel, then the kernel module should be automatically loaded when <citerefentry><refentrytitle>mdconfig</refentrytitle><manvolnum>8</manvolnum></citerefentry> is executed during the boot media creation phase. All of the tools necessary to build a release are available from the Subversion repository in <filename>src/release</filename>. 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 <acronym>ISO</acronym> images suitable for burning to CDROM or DVD, and an FTP install directory. <citerefentry><refentrytitle>release</refentrytitle><manvolnum>7</manvolnum></citerefentry> fully documents the <command>src/release/generate-release.sh</command> script which is used to build a release. <command>generate-release.sh</command> is a wrapper around the Makefile target: <command>make release</command>.
Building a Release
<citerefentry><refentrytitle>release</refentrytitle><manvolnum>7</manvolnum></citerefentry> documents the exact commands required to build a FreeBSD release. The following sequences of commands can build an 9.2.0 release:
<prompt>#</prompt> <userinput>cd /usr/src/release</userinput>
<prompt>#</prompt> <userinput>sh generate-release.sh release/9.2.0 /local3/release</userinput>
After running these commands, all prepared release files are available in <filename>/local3/release/R</filename> directory.
The release <filename>Makefile</filename> can be broken down into several distinct steps.
Creation of a sanitized system environment in a separate directory hierarchy with <quote><command>make installworld</command></quote>.
Checkout from Subversion of a clean version of the system source, documentation, and ports into the release build hierarchy.
Population of <filename>/etc</filename> and <filename>/dev</filename> in the chrooted environment.
chroot into the release build hierarchy, to make it harder for the outside environment to taint this build.
<command>make world</command> in the chrooted environment.
Build of Kerberos-related binaries.
Build <filename>GENERIC</filename> kernel.
Creation of a staging directory tree where the binary distributions will be built and packaged.
Build and installation of the documentation toolchain needed to convert the documentation source (SGML) into HTML and text documents that will accompany the release.
Build and installation of the actual documentation (user manuals, tutorials, release notes, hardware compatibility lists, and so on.)
Package up distribution tarballs of the binaries and sources.
Create FTP installation hierarchy.

Loading…

No matching activity found.

Browse all component changes

Source information

Source string comment
(itstool) path: sect2/para
Flags
read-only
Source string location
article.translate.xml:628
String age
a year ago
Source string age
a year ago
Translation file
articles/releng.pot, string 115