Translation

(itstool) path: row/entry
<filename>UPDATING</filename>
29/290
Context English Portuguese (Brazil) State
The <literal>EVERYTHINGISFINE</literal> variable name was chosen to avoid colliding with a variable that might be possibly set in the user environment, accidentally enabling the behavior that depends on it being defined.
O nome da variável <literal>EVERYTHINGISFINE</literal> foi escolhido para evitar a colisão com uma variável possivelmente definida no ambiente do usuário, ativando acidentalmente o comportamento que depende de sua definição.
As <filename>thermite.sh</filename> iterates through the master list of combinations and locates the per-build configuration file, a <acronym>ZFS</acronym> dataset is created under <filename class="directory">/releng</filename>, such as <filename class="directory">/releng/12-amd64-GENERIC-snap</filename>. The <literal>src/</literal>, <literal>ports/</literal>, and <literal>doc/</literal> trees are checked out to separate <acronym>ZFS</acronym> datasets, such as <filename class="directory">/releng/12-src-snap</filename>, which are then cloned and mounted into the respective build datasets. This is done to avoid checking out a given tree more than once.
Como o <filename>thermite.sh</filename> percorre a lista principal de combinações e localiza o arquivo de configuração por compilação, um dataset <acronym>ZFS</acronym> é criado sob o <filename class="directory">/releng</filename>, tal como <filename class="directory">/releng/12-amd64-GENERIC-snap</filename>. O checkout das árvores <literal>src/</literal>, <literal>ports/</literal> e <literal>doc/</literal> é realizado em diferentes datasets <acronym>ZFS</acronym>, tal como <filename class="directory">/releng/12-src-snap</filename>, os quais são então clonados e montados nos respectivos datasets de compilação. Isso é feito para evitar a remoção de uma determinada árvore mais de uma vez.
Assuming these filesystem paths, <filename>thermite.sh</filename> would be invoked as:
Assumindo esses caminhos do sistema de arquivos, o <filename>thermite.sh</filename> deveria ser chamado como:
<prompt>#</prompt> <userinput>cd /releng/scripts-snapshot/scripts</userinput>
<prompt>#</prompt> <userinput>./setrev.sh -b <literal>stable/<replaceable>12</replaceable>/</literal></userinput>
<prompt>#</prompt> <userinput>./zfs-cleanup.sh -c ./builds-<replaceable>12</replaceable>.conf</userinput>
<prompt>#</prompt> <userinput>./thermite.sh -c ./builds-<replaceable>12</replaceable>.conf</userinput>
<prompt>#</prompt> <userinput>cd /releng/scripts-snapshot/scripts</userinput>
<prompt>#</prompt> <userinput>./setrev.sh -b <literal>stable/<replaceable>12</replaceable>/</literal></userinput>
<prompt>#</prompt> <userinput>./zfs-cleanup.sh -c ./builds-<replaceable>12</replaceable>.conf</userinput>
<prompt>#</prompt> <userinput>./thermite.sh -c ./builds-<replaceable>12</replaceable>.conf</userinput>
Once the builds have completed, additional helper scripts are available to generate development snapshot emails which are sent to the <literal>freebsd-snapshots@freebsd.org</literal> mailing list:
Quando as compilações forem concluídas, scripts adicionais auxiliares estarão disponíveis para gerar e-mails de snapshots de desenvolvimento que são enviados para a lista de e-mail <literal>freebsd-snapshots@freebsd.org</literal>:
<prompt>#</prompt> <userinput>cd /releng/scripts-snapshot/scripts</userinput>
<prompt>#</prompt> <userinput>./get-checksums.sh -c ./builds-<replaceable>12</replaceable>.conf | ./generate-email.pl &gt; snapshot-<replaceable>12</replaceable>-mail</userinput>
<prompt>#</prompt> <userinput>cd /releng/scripts-snapshot/scripts</userinput>
<prompt>#</prompt> <userinput>./get-checksums.sh -c ./builds-<replaceable>12</replaceable>.conf | ./generate-email.pl &gt; snapshot-<replaceable>12</replaceable>-mail</userinput>
The generated output should be double-checked for correctness, and the email itself should be PGP signed, in-line.
A saída gerada deve ser checada duas vezes para garantir a exatidão, e o próprio e-mail deve ter assinatura PGP, in-line (no arquivo).
These helper scripts only apply to development snapshot builds. Announcements during the release cycle (excluding the final release announcement) are created from an email template. A sample of the email template currently used can be found <link xlink:href="https://svn.freebsd.org/base/user/gjb/thermite/non-release-template-mail.txt">here</link>.
Esses scripts auxiliares aplicam-se apenas às compilações de snapshot (versão instantânea) de desenvolvimento. Os anúncios durante o ciclo de lançamento (excluindo o anúncio de versão final) são criados a partir de um modelo de email. Uma amostra do modelo de email usado atualmente pode ser encontrada <link xlink:href="https://svn.freebsd.org/base/user/gjb/thermite/non-release-template-mail.txt">aqui</link>.
Building FreeBSD Releases
Construindo Releases do FreeBSD
Similar to building FreeBSD development snapshots, <filename>thermite.sh</filename> would be invoked the same way. The difference between development snapshots and release builds, <literal>BETA</literal> and <literal>RC</literal> included, is that the <citerefentry><refentrytitle>chroot</refentrytitle><manvolnum>8</manvolnum></citerefentry> configuration files must be named with <literal>release</literal> instead of <literal>snap</literal> as the "type", as mentioned above.
Similar a compilação de snapshots de desenvolvimento do FreeBSD, o <filename>thermite.sh</filename> seria invocado da mesma maneira. A diferença entre snapshots de desenvolvimento e builds de releases, <literal>BETA</literal> e <literal>RC</literal> inclusos, é que os arquivos de configuração do <citerefentry><refentrytitle>chroot</refentrytitle><manvolnum>8</manvolnum></citerefentry> devem ser nomeados com <literal>release</literal> ao invés de <literal>snap</literal> no "type", como mencionado acima.
In addition, the <literal>BUILDTYPE</literal> and <literal>types</literal> must be changed from <literal>snap</literal> to <literal>release</literal> in <filename>defaults-<replaceable>12</replaceable>.conf</filename> and <filename>builds-<replaceable>12</replaceable>.conf</filename>, respectively.
Além disso, <literal>BUILDTYPE</literal> e <literal>types</literal> devem ser alterados de <literal>snap</literal> para <literal>release</literal> em <filename>defaults-<replaceable>12</replaceable>.conf</filename> e <filename>builds-<replaceable>12</replaceable>.conf</filename>, respectivamente.
When building <literal>BETA</literal>, <literal>RC</literal>, and the final <literal>RELEASE</literal>, also statically set <literal>BUILDSVNREV</literal> to the revision on the branch reflecting the name change, <literal>BUILDDATE</literal> to the date the builds are started in <literal>YYYYMMDD</literal> format. If the <literal>doc/</literal> and <literal>ports/</literal> trees have been tagged, also set <literal>PORTBRANCH</literal> and <literal>DOCBRANCH</literal> to the relevant tag path in the Subversion repository, replacing <literal>HEAD</literal> with the last changed revision. Also set <literal>releasesrc</literal> in <filename>builds-<replaceable>12</replaceable>.conf</filename> to the relevant branch, such as <literal>stable/<replaceable>12</replaceable>/</literal> or <literal>releng/<replaceable>12.0</replaceable>/</literal>.
Ao construir o <literal>BETA</literal>, o <literal>RC</literal>, e o <literal>RELEASE</literal> final, também ajuste estaticamente o <literal>BUILDSVNREV</literal> para a revisão na branch refletindo a mudança de nome, <literal>BUILDDATE</literal> para a data em que as compilações são iniciadas no formato <literal>YYYYMMDD</literal>. Se as árvores <literal>doc/</literal> e <literal>ports/</literal> tiverem sido marcadas, defina também o <literal>PORTBRANCH</literal> e o <literal>DOCBRANCH</literal> para o caminho da tag relevante no repositório Subversion, substituindo <literal>HEAD</literal> pela última revisão alterada. Também defina <literal>releasesrc</literal> em <filename>builds-<replaceable>12</replaceable>.conf </filename> para a branch relevante, como <literal>stable/<replaceable>12</replaceable>/</literal> ou <literal>releng/<replaceable>12.0</replaceable>/</literal>.
During the release cycle, a copy of <filename>CHECKSUM.SHA512</filename> and <filename>CHECKSUM.SHA256</filename> for each architecture are stored in the FreeBSD Release Engineering Team internal repository in addition to being included in the various announcement emails. Each <filename>MANIFEST</filename> containing the hashes of <filename>base.txz</filename>, <filename>kernel.txz</filename>, etc. are added to <package>misc/freebsd-release-manifests</package> in the Ports Collection, as well.
Durante o ciclo de release, uma cópia do <filename>CHECKSUM.SHA512</filename> e do <filename>CHECKSUM.SHA256</filename> para cada arquitetura é armazenada no repositório interno da Equipe de Engenharia de Release do FreeBSD, além de ser incluída nos diversos e-mails de anúncio. Cada <filename>MANIFEST</filename> contendo os hashes do <filename>base.txz</filename>, do <filename>kernel.txz</filename>, etc. também são adicionados ao <package>misc/freebsd-release-manifests</package> na coleção de ports.
In preparation for the release build, several files need to be updated:
Na preparação para a compilação da release, vários arquivos precisam ser atualizados:
Update the <varname>BRANCH</varname> value to <literal>RELEASE</literal>
Atualize o valor <varname>BRANCH</varname> para <literal>RELEASE</literal>
<filename>UPDATING</filename>
<filename>UPDATING</filename>
Add the anticipated announcement date
Adicione a data prevista do anúncio
<filename>lib/csu/common/crtbrand.c</filename>
<filename>lib/csu/common/crtbrand.c</filename>
Replace <literal>__FreeBSD_version</literal> with the value in <filename>sys/sys/param.h</filename>
Altere <literal>__FreeBSD_version</literal> com o valor em <filename>sys/sys/param.h</filename>
After building the final <literal>RELEASE</literal>, the <literal>releng/<replaceable>12.0</replaceable>/</literal> branch is tagged as <literal>release/<replaceable>12.0.0</replaceable>/</literal> using the revision from which the <literal>RELEASE</literal> was built. Similar to creating the <literal>stable/<replaceable>12</replaceable>/</literal> and <literal>releng/<replaceable>12.0</replaceable>/</literal> branches, this is done with <command>svn cp</command>. From the repository root:
Depois de construir a <literal>RELEASE</literal> final, a branch <literal>releng/<replaceable>12.0</replaceable>/</literal> é marcada como <literal>release/<replaceable>12.0.0</replaceable>/</literal> usando a revisão a partir da qual a <literal>RELEASE</literal> foi construída. Semelhante a criar as branches <literal>stable/<replaceable>12</replaceable>/</literal> e <literal>releng/<replaceable>12.0</replaceable>/</literal>, isso é feito com <command>svn cp</command>. Da raiz do repositório:
<prompt>%</prompt> <userinput>svn cp ^/<literal>releng/<replaceable>12.0</replaceable>/</literal>@r<replaceable>306420</replaceable> <literal>release/<replaceable>12.0.0</replaceable>/</literal></userinput>
<prompt>%</prompt> <userinput>svn commit <literal>release/<replaceable>12.0.0</replaceable>/</literal></userinput>
<prompt>%</prompt> <userinput>svn cp ^/<literal>releng/<replaceable>12.0</replaceable>/</literal>@r<replaceable>306420</replaceable> <literal>release/<replaceable>12.0.0</replaceable>/</literal></userinput>
<prompt>%</prompt> <userinput>svn commit <literal>release/<replaceable>12.0.0</replaceable>/</literal></userinput>
Publishing FreeBSD Installation Media to Project Mirrors
Publicando a Mídia de Instalação do FreeBSD nos Espelhos do Projeto
This section describes the procedure to publish FreeBSD development snapshots and releases to the Project mirrors.
Esta seção descreve o procedimento para publicar snapshots e releases de desenvolvimento do FreeBSD nos espelhos do Projeto.
Staging FreeBSD Installation Media Images
Preparando Imagens de Mídias de Instalação do FreeBSD
Staging FreeBSD snapshots and releases is a two part process:
A preparação dos snapshots e das versões do FreeBSD é um processo de duas partes:
Creating the directory structure to match the hierarchy on <systemitem>ftp-master</systemitem>
Criando a estrutura de diretórios para corresponder a hierarquia em <systemitem>ftp-master</systemitem>
If <literal>EVERYTHINGISFINE</literal> is defined in the build configuration files, <filename>main.conf</filename> in the case of the build scripts referenced above, this happens automatically in the <citerefentry><refentrytitle>chroot</refentrytitle><manvolnum>8</manvolnum></citerefentry> after the build is complete, creating the directory structure in <filename class="directory">${DESTDIR}/R/ftp-stage</filename> with a path structure matching what is expected on <systemitem>ftp-master</systemitem>. This is equivalent to running the following in the <citerefentry><refentrytitle>chroot</refentrytitle><manvolnum>8</manvolnum></citerefentry> directly:
Se <literal>EVERYTHINGISFINE</literal> for definido nos arquivos de configuração de compilação, <filename>main.conf</filename> no caso dos scripts de compilação mencionados acima, isto acontece automaticamente no <citerefentry><refentrytitle>chroot</refentrytitle><manvolnum>8</manvolnum></citerefentry> após a compilação ser concluída, criando a estrutura de diretório em <filename class="directory">${DESTDIR}/R/ftp-stage</filename> com um estrutura de caminho que corresponde ao que é esperado em <systemitem>ftp-master</systemitem>. Isto é equivalente a executar o seguinte diretamente no <citerefentry><refentrytitle>chroot</refentrytitle> <manvolnum>8</manvolnum></citerefentry>:
<prompt>#</prompt> <userinput>make -C /usr/src/release -f Makefile.mirrors EVERYTHINGISFINE=1 ftp-stage</userinput>
<prompt>#</prompt> <userinput>make -C /usr/src/release -f Makefile.mirrors EVERYTHINGISFINE=1 ftp-stage</userinput>
After each architecture is built, <filename>thermite.sh</filename> will <application>rsync</application> the <filename class="directory">${DESTDIR}/R/ftp-stage</filename> from the build <citerefentry><refentrytitle>chroot</refentrytitle><manvolnum>8</manvolnum></citerefentry> to <filename class="directory">/snap/ftp/snapshots</filename> or <filename class="directory">/snap/ftp/releases</filename> on the build host, respectively.
Depois que cada arquitetura é compilada, o <filename>thermite.sh</filename> irá fazer um <application>rsync</application> do <filename class="directory">${DESTDIR}/R/ftp-stage</filename> da compilação <citerefentry><refentrytitle>chroot</refentrytitle><manvolnum>8</manvolnum></citerefentry> para o diretório <filename class="directory">/snap/ftp/snapshots</filename> ou <filename class="directory">/snap/ftp/releases</filename> no host de compilação, respectivamente.
Copying the files to a staging directory on <systemitem>ftp-master</systemitem> before moving the files into <filename class="directory">pub/</filename> to begin propagation to the Project mirrors
Copiando os arquivos para um diretório temporário em <systemitem>ftp-master </systemitem> antes de mover os arquivos para <filename class="directory">pub/</filename> para iniciar a propagação para os servidores espelhos do Projeto
Once all builds have finished, <filename class="directory">/snap/ftp/snapshots</filename>, or <filename class="directory">/snap/ftp/releases</filename> for a release, is polled by <systemitem>ftp-master</systemitem> using <application>rsync</application> to <filename class="directory">/archive/tmp/snapshots</filename> or <filename class="directory">/archive/tmp/releases</filename>, respectively.
Uma vez que todas as compilações terminarem, <filename class="directory">/snap/ftp/snapshots</filename>, ou <filename class="directory">/snap/ftp/releases</filename> para uma versão, é pesquisado pelo <systemitem>ftp-master</systemitem> usando <application>rsync</application> para <filename class="directory">/archive/tmp/snapshots</filename> ou <filename class="directory">/archive/tmp/releases</filename>, respectivamente.

Loading…

<filename>UPDATING</filename>
<filename>head/UPDATING</filename>
2 months ago
User avatar None

Source string changed

FreeBSD Doc / articles_freebsd-relengPortuguese (Brazil)

<filename>head/UPDATING</filename>
2 months ago
Browse all component changes

Glossary

English Portuguese (Brazil)
No related strings found in the glossary.

Source information

Source string comment
(itstool) path: row/entry
Labels
No labels currently set.
Source string location
article.translate.xml:1395
Source string age
2 months ago
Translation file
articles/pt_BR/freebsd-releng.po, string 268