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

Source string Read only

(itstool) path: sect3/para
Context English State
Update <literal>BETA<replaceable>X</replaceable></literal> with <literal>PRERELEASE</literal>
Add a new approvers line for the releng branch as was done for the stable branch
<prompt>%</prompt> <userinput>svn propdel -R svn:mergeinfo <literal>releng/<replaceable>12.0</replaceable>/</literal></userinput>
<prompt>%</prompt> <userinput>svn commit <literal>releng/<replaceable>12.0</replaceable>/</literal></userinput>
<prompt>%</prompt> <userinput>svn commit <literal>stable/<replaceable>12</replaceable>/</literal></userinput>
Now that two new <varname>__FreeBSD_version</varname> values exist, also update <filename>head/en_US.ISO8859-1/books/porters-handbook/versions/chapter.xml</filename> in the Documentation Project repository.
After the first <literal>RC</literal> build has completed and tested, the <literal>stable/</literal> branch can be <quote>thawed</quote> by removing (or commenting) the ^/<literal>stable/<replaceable>12</replaceable>/</literal> entry in <filename>svnadmin/conf/approvers</filename>.
Following the availability of the first <literal>RC</literal>, FreeBSD Bugmeister Team should be emailed to add the new FreeBSD <literal>-RELEASE</literal> to the <literal>versions</literal> available in the drop-down menu shown in the bug tracker.
Building FreeBSD Installation Media
This section describes the general procedures producing FreeBSD development snapshots and releases.
Release Build Scripts
This section describes the build scripts used by FreeBSD Release Engineering Team to produce development snapshots and releases.
The <filename></filename> Script
Prior to FreeBSD 9.0-RELEASE, <filename>src/release/Makefile</filename> was updated to support <citerefentry><refentrytitle>bsdinstall</refentrytitle><manvolnum>8</manvolnum></citerefentry>, and the <filename>src/release/</filename> script was introduced as a wrapper to automate invoking the <citerefentry><refentrytitle>release</refentrytitle><manvolnum>7</manvolnum></citerefentry> targets.
Prior to FreeBSD 9.2-RELEASE, <filename>src/release/</filename> was introduced, which heavily based on <filename>src/release/</filename> included support to specify configuration files to override various options and environment variables. Support for configuration files provided support for cross building each architecture for a release by specifying a separate configuration file for each invocation.
As a brief example of using <filename>src/release/</filename> to build a single release in <filename class="directory">/scratch</filename>:
<prompt>#</prompt> <userinput>/bin/sh /usr/src/release/</userinput>
As a brief example of using <filename>src/release/</filename> to build a single, cross-built release using a different target directory, create a custom <filename>release.conf</filename> containing:
# configuration for powerpc/powerpc64
Then invoke <filename>src/release/</filename> as:
<prompt>#</prompt> <userinput>/bin/sh /usr/src/release/ -c <replaceable>$HOME/release.conf</replaceable></userinput>
See <citerefentry><refentrytitle>release</refentrytitle><manvolnum>7</manvolnum></citerefentry> and <filename>src/release/release.conf.sample</filename> for more details and example usage.
The <filename></filename> Wrapper Script
In order to make cross building the full set of architectures supported on a given branch faster, easier, and reduce human error factors, a wrapper script around <filename>src/release/</filename> was written to iterate through the various combinations of architectures and invoke <filename>src/release/</filename> using a configuration file specific to that architecture.
The wrapper script is called <filename></filename>, which is available in the FreeBSD Subversion repository at <literal>svn://</literal>, in addition to configuration files used to build <literal>head/</literal> and <literal>stable/<replaceable>12</replaceable>/</literal> development snapshots.
Using <filename></filename> is covered in <xref linkend="releng-build-snapshot"/> and <xref linkend="releng-build-release"/>.
Each architecture and individual kernel have their own configuration file used by <filename></filename>. Each branch has its own <filename>defaults-X.conf</filename> configuration which contains entries common throughout each architecture, where overrides or special variables are set and/or overridden in the per-build files.
The per-build configuration file naming scheme is in the form of <filename>${revision}-${TARGET_ARCH}-${KERNCONF}-${type}.conf</filename>, where the uppercase variables are equivalent to what <citerefentry><refentrytitle>make</refentrytitle><manvolnum>1</manvolnum></citerefentry> uses in the build system, and lowercase variables are set within the configuration files, mapping to the major version of the respective branch.
Each branch also has its own <filename>builds-X.conf</filename> configuration, which is used by <filename></filename>. The <filename></filename> script iterates through each ${revision}, ${TARGET_ARCH}, ${KERNCONF}, and ${type} value, creating a master list of what to build. However, a given combination from the list will only be built if the respective configuration file exists, which is where the naming scheme above is relevant.
There are two paths of file sourcing:


New source string 10 months ago
Browse all component changes

Source information

Source string comment
(itstool) path: sect3/para
Source string location
String age
10 months ago
Source string age
10 months ago
Translation file
articles/freebsd-releng.pot, string 228