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


(itstool) path: sect1/para
This section describes the procedure to publish FreeBSD development snapshots and releases to the Project mirrors.
Context English Portuguese (Brazil) State
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="">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="">aqui</link>.
Building FreeBSD Releases Construindo Releases do FreeBSD
Similar to building FreeBSD development snapshots, <filename></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></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></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></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.
On <systemitem>ftp-master</systemitem> in the FreeBSD Project infrastructure, this step requires <literal>root</literal> level access, as this step must be executed as the <literal>archive</literal> user. No <systemitem>ftp-master</systemitem> na infraestrutura do Projeto FreeBSD, esta etapa requer acesso ao nível de <literal>root</literal>, já que esta etapa deve ser executada como o usuário <literal>archive</literal>.
Publishing FreeBSD Installation Media Publicando a Mídia de Instalação do FreeBSD
Once the images are staged in <filename class="directory">/archive/tmp/</filename>, they are ready to be made public by putting them in <filename class="directory">/archive/pub/FreeBSD</filename>. In order to reduce propagation time, <citerefentry><refentrytitle>pax</refentrytitle><manvolnum>1</manvolnum></citerefentry> is used to create hard links from <filename class="directory">/archive/tmp</filename> to <filename class="directory">/archive/pub/FreeBSD</filename>. Uma vez que as imagens são colocadas em <filename class="directory">/archive/tmp/</filename>, elas estão prontas para serem publicadas colocando-as em <filename class="directory">/archive/pub/FreeBSD</filename>. Para reduzir o tempo de propagação, o <citerefentry><refentrytitle>pax</refentrytitle><manvolnum>1</manvolnum></citerefentry> é usado para criar links físicos a partir de <filename class="directory">/archive/tmp</filename> para <filename class="directory">/archive/pub/FreeBSD</filename>.
In order for this to be effective, both <filename class="directory">/archive/tmp</filename> and <filename class="directory">/archive/pub</filename> must reside on the same logical filesystem. Para que isto seja efetivo, tanto o <filename class="directory">/archive/tmp</filename> quanto o <filename class="directory">/archive/pub</filename> devem residir no mesmo sistema de arquivos lógico.
There is a caveat, however, where <application>rsync</application> must be used after <citerefentry><refentrytitle>pax</refentrytitle><manvolnum>1</manvolnum></citerefentry> in order to correct the symbolic links in <filename class="directory">pub/FreeBSD/<replaceable>snapshots</replaceable>/ISO-IMAGES</filename> which <citerefentry><refentrytitle>pax</refentrytitle><manvolnum>1</manvolnum></citerefentry> will replace with a hard link, increasing the propagation time. Há uma ressalva, no entanto, em que o <application>rsync</application> deve ser usado após o <citerefentry><refentrytitle>pax</refentrytitle><manvolnum>1</manvolnum></citerefentry> para corrigir os links simbólicos no <filename class="directory">pub/FreeBSD/<replaceable>snapshots</replaceable>/ISO-IMAGES</filename> que o <citerefentry><refentrytitle>pax</refentrytitle><manvolnum>1</manvolnum></citerefentry> irá substituir por um hard link, aumentando o tempo de propagação.
As with the staging steps, this requires <literal>root</literal> level access, as this step must be executed as the <literal>archive</literal> user. Assim como nas etapas de preparação, isto requer acesso em nível de <literal>root</literal>, já que essa etapa deve ser executada como o usuário <literal>archive</literal>.
As the <literal>archive</literal> user: Como o usuário <literal>archive</literal>:


No matching activity found.

Browse all component changes


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

Source information

Source string comment
(itstool) path: sect1/para
Source string location
String age
a year ago
Source string age
a year ago
Translation file
articles/pt_BR/freebsd-releng.po, string 275