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


(itstool) path: tip/screen
<prompt>#</prompt> <userinput>poudriere jail -u -J 6 -j <replaceable>JAILNAME</replaceable></userinput>
Context English Portuguese (Brazil) State
Create <literal>tank/poudriere/jails/11i386</literal>, mount it on <filename>/poudriere/jails/11i386</filename>, then check out the tip of the <application>Subversion</application> branch of <literal>FreeBSD-11-STABLE</literal> from <literal>SVN_HOST</literal> in <filename>poudriere.conf</filename> into <filename>/poudriere/jails/11i386/usr/src</filename>, then complete a <_:buildtarget-1/> and install it into <filename>/poudriere/jails/11i386</filename>. Criado o <literal>tank/poudriere/jaulas/11i386</literal> monte-o em <filename>/poudriere/jails/11i386</filename>, então confira a dica do <application>Subversion</application> branch do <literal>FreeBSD-11-STABLE</literal> a partir do <literal>SVN_HOST</literal> dentro do <filename>poudriere.conf</filename> para dentro de <filename>/poudriere/jails/11i386/usr/src</filename>, e então complete um <_:buildtarget-1/> e instale-o em <filename>/poudriere/jails/11i386</filename>.
If a specific <application>Subversion</application> revision is needed, append it to the version string. For example: Se uma determinada revisão do <application>Subversion</application> é necessária, anexe ela à string de versão. Por exemplo:
<prompt>#</prompt> <userinput>poudriere jail -c -j 11i386 -v stable/11@123456 -a i386 -m svn+https</userinput> <prompt>#</prompt> <userinput>poudriere jail -c -j 11i386 -v stable/11@123456 -a i386 -m svn+https</userinput>
While it is possible to build a newer version of FreeBSD on an older version, most of the time it will not run. For example, if a <literal>stable/11</literal> jail is needed, the host will have to run <literal>stable/11</literal> too. Running <literal>11.3-RELEASE</literal> is not enough. Embora seja possível compilar uma versão mais nova do FreeBSD em uma versão mais antiga, na maioria das vezes ela não irá executar. Por exemplo, se uma jail <literal>stable/11</literal> é necessária, o host terá que rodar <literal>stable/11</literal> também. Rodar <literal>11.3-RELEASE</literal> não é o suficiente.
To create a <application>Poudriere</application> jail for <literal>13.0-CURRENT</literal>: Para criar uma jail <application>Poudriere</application> para o <literal>13.0-CURRENT</literal>:
<prompt>#</prompt> <userinput>poudriere jail -c -j 13amd64 -v head -a amd64 -m svn+https</userinput> <prompt>#</prompt> <userinput>poudriere jail -c -j 13amd64 -v head -a amd64 -m svn+https</userinput>
In order to run a <literal>13.0-CURRENT</literal> <application>Poudriere</application> jail you must be running <literal>13.0-CURRENT</literal>. In general, newer kernels can build and run older jails. For instance, a <literal>13.0-CURRENT</literal> kernel can build and run a <literal>11.3-STABLE</literal> <application>Poudriere</application> jail if the <literal>COMPAT_FREEBSD11</literal> kernel option was compiled in (on by default in <literal>13.0-CURRENT</literal> <filename>GENERIC</filename> kernel config). Para executar uma jail <literal>13.0-CURRENT</literal> no <application>Poudriere</application> você deve estar rodando o <literal>13.0-CURRENT</literal>. Em geral, novos kernels podem ser compilados e executar jails mais antigas. Por exemplo, um kernel <literal>13.0-CURRENT</literal> pode compilar e executar uma jail <literal>11.3-STABLE</literal> no <application>Poudriere</application> se a opção de kernel <literal>COMPAT_FREEBSD11</literal> tiver sido compilada (habilitada por padrão na configuração do kernel <filename>GENERIC</filename> do <literal>13.0-CURRENT</literal>).
The default <literal>svn</literal> protocol works but is not very secure. Using <literal>svn+https</literal> along with verifying the remote server's <acronym>SSL</acronym> fingerprint is advised. It will ensure that the files used for building the jail are from a trusted source. O protocolo padrão <literal>svn</literal> funciona normalmente, mas não é muito seguro. Usar <literal>svn+https</literal> juntamente com a verificação do fingerpprint <acronym>SSL</acronym> do servidor remoto é aconselhável. Isso garantirá que os arquivos usados para compilar a jail sejam de uma fonte confiável.
A list of jails currently known to <application>Poudriere</application> can be shown with <command>poudriere jail -l</command>: Uma lista de jails atualmente conhecidas pelo <application>Poudriere</application> podem ser mostradas com <command>poudriere jail -l</command>:
<prompt>#</prompt> <userinput>poudriere jail -l</userinput>
113Ramd64 11.3-RELEASE amd64 ftp
11i386 11.3-STABLE i386 svn+https
<prompt>#</prompt> <userinput>poudriere jail -l</userinput>
113Ramd64 11.3-RELEASE amd64 ftp
11i386 11.3-STABLE i386 svn+https
Keeping <application>Poudriere</application> Jails Updated Mantendo as Jails do <application>Poudriere</application> Atualizadas
Managing updates is very straightforward. The command: Gerenciar atualizações é muito simples. O comando:
<prompt>#</prompt> <userinput>poudriere jail -u -j <replaceable>JAILNAME</replaceable></userinput> <prompt>#</prompt> <userinput>poudriere jail -u -j <replaceable>JAILNAME</replaceable></userinput>
updates the specified jail to the latest version available. For FreeBSD releases, update to the latest patchlevel with <citerefentry><refentrytitle>freebsd-update</refentrytitle><manvolnum>8</manvolnum></citerefentry>. For FreeBSD versions built from source, update to the latest <application>Subversion</application> revision in the branch. atualiza a jail especificada para a versão mais recente disponível. Para releases do FreeBSD, atualiza para o patchlevel mais recente com o <citerefentry><refentrytitle>freebsd-update</refentrytitle><manvolnum>8</manvolnum></citerefentry>. Para versões do FreeBSD compiladas a partir do código fonte, atualiza para a revisão mais recente na branch do <application>Subversion</application>.
For jails employing a <literal>svn+<replaceable>*</replaceable></literal> method, it is helpful to add <command>-J <replaceable>NumberOfParallelBuildJobs</replaceable></command> to speed up the build by increasing the number of parallel compile jobs used. For example, if the building machine has 6 <acronym>CPU</acronym>s, use: Para jails que empregam um método <literal>svn+<replaceable>*</replaceable></literal>, é útil adicionar <command>-J <replaceable>NumberOfParallelBuildJobs</replaceable></command> para acelerar a compilação aumentando o número de trabalhos de compilação paralelos utilizados. Por exemplo, se a máquina de compilação tiver 6 <acronym>CPU</acronym>s, use:
<prompt>#</prompt> <userinput>poudriere jail -u -J 6 -j <replaceable>JAILNAME</replaceable></userinput> <prompt>#</prompt> <userinput>poudriere jail -u -J 6 -j <replaceable>JAILNAME</replaceable></userinput>
Setting Up Ports Trees for Use with <application>Poudriere</application> Configurando a Árvores de Ports para Uso com o <application>Poudriere</application>
There are multiple ways to use ports trees in <application>Poudriere</application>. The most straightforward way is to have <application>Poudriere</application> create a default ports tree for itself, using either <citerefentry><refentrytitle>portsnap</refentrytitle><manvolnum>8</manvolnum></citerefentry> (if running FreeBSD 12.1 or 11.4) or <application>Subversion</application> (if running FreeBSD-CURRENT): Existem várias maneiras de usar árvores de ports no <application>Poudriere</application>. A maneira mais direta é o <application>Poudriere</application> criar uma árvore de ports padrão para si mesmo usando <citerefentry><refentrytitle>portsnap</refentrytitle><manvolnum>8</manvolnum></citerefentry> (se estiver executando FreeBSD 12.1 ou 11.4) ou <application>Subversion</application> (se estiver executando FreeBSD-CURRENT):
<prompt>#</prompt> <userinput>poudriere ports -c -m portsnap</userinput> <prompt>#</prompt> <userinput>poudriere ports -c -m portsnap</userinput>
<prompt>#</prompt> <userinput>poudriere ports -c -m svn+https</userinput> <prompt>#</prompt> <userinput>poudriere ports -c -m svn+https</userinput>
These commands create <literal>tank/poudriere/ports/default</literal>, mount it on <filename>/poudriere/ports/default</filename>, and populate it using either <citerefentry><refentrytitle>portsnap</refentrytitle><manvolnum>8</manvolnum></citerefentry> or <application>Subversion</application>. Afterward it is included in the list of known ports trees: Estes comandos criam <literal>tank/poudriere/ports/default</literal>, monta-o em <filename>/poudriere/ports/default</filename> e o povoa usando o <citerefentry><refentrytitle>portsnap</refentrytitle><manvolnum>8</manvolnum></citerefentry> ou <application>Subversion</application>. Depois disso, ele é incluído na lista de árvores de ports conhecidas:
<prompt>#</prompt> <userinput>poudriere ports -l</userinput>
default svn+https 2020-07-20 04:23:56 /poudriere/ports/default
<prompt>#</prompt> <userinput>poudriere ports -l</userinput>
default svn+https 2020-07-20 04:23:56 /poudriere/ports/default
Note that the <quote>default</quote> ports tree is special. Each of the build commands explained later will implicitly use this ports tree unless specifically specified otherwise. To use another tree, add <command>-p <replaceable>treename</replaceable></command> to the commands. Note que a árvore de ports <quote>default</quote> é especial. Cada um dos comandos de compilação explicados posteriormente usará implicitamente essa árvore de ports, a menos que seja especificamente especificado de outra forma. Para usar outra árvore, adicione <command>-p <replaceable>treename</replaceable></command> aos comandos.
While useful for regular bulk builds, having this default ports tree with the <citerefentry><refentrytitle>portsnap</refentrytitle><manvolnum>8</manvolnum></citerefentry> method may not be the best way to deal with local modifications for a ports contributor. As with the creation of jails, it is possible to use a different method for creating the ports tree. To add an additional ports tree for testing local modifications and ports development, checking out the tree via <application>Subversion</application> (as described above) is preferable. Embora seja útil para compilações em massa regulares, ter esta árvore de ports padrão com o método <citerefentry><refentrytitle>portsnap</refentrytitle><manvolnum>8</manvolnum></citerefentry> pode não ser a melhor maneira de lidar com modificações locais para um contribuidor de ports. Assim como na criação dos jails, é possível usar um método diferente para criar a árvore de ports. Para adicionar uma árvore de ports adicional para testar modificações locais e para o desenvolvimento de ports, baixar a árvore via <application>Subversion</application> (como descrito acima) é preferido:
The <acronym>http</acronym> and <acronym>https</acronym> methods need <package role="port">devel/subversion</package> built with the <literal>SERF</literal> option enabled. It is enabled by default. Os métodos <acronym>http</acronym> e <acronym>https</acronym> precisam que o <package role="port">devel/subversion</package> seja compilado com a opção <literal>SERF</literal> ativada. Ela vem habilitada por padrão.
The <literal>svn</literal> method allows extra qualifiers to tell <application>Subversion</application> exactly how to fetch data. This is explained in <citerefentry vendor="ports"><refentrytitle>poudriere</refentrytitle><manvolnum>8</manvolnum></citerefentry>. For instance, <command>poudriere ports -c -m svn+ssh -p subversive</command> uses <application>SSH</application> for the checkout. O método <literal>svn</literal> permite qualificadores extras para dizer ao <application>Subversion</application> exatamente como buscar os dados. Isso é explicado em <citerefentry vendor="ports"><refentrytitle>poudriere</refentrytitle><manvolnum>8</manvolnum></citerefentry>. Por exemplo, <command>poudriere ports -c -m svn+ssh -p subversive</command> usa o <application>SSH</application> para o checkout.
Using Manually Managed Ports Trees with Poudriere Usando Árvores de Ports Gerenciadas Manualmente com o Poudriere
Depending on the workflow, it can be extremely helpful to use ports trees which are maintained manually. For instance, if there is a local copy of the ports tree in <filename>/work/ports</filename>, point <application>Poudriere</application> to the location: Dependendo do fluxo de trabalho, pode ser extremamente útil usar árvores de ports que são mantidas manualmente. Por exemplo, se houver uma cópia local da árvore de ports em <filename>/work/ports</filename>, aponte o <application>Poudriere</application> para o local:
For <application>Poudriere</application> older than version 3.1.20: Para o <application>Poudriere</application> anterior à versão 3.1.20:
<prompt>#</prompt> <userinput>poudriere ports -c -F -f none -M /work/ports -p development</userinput> <prompt>#</prompt> <userinput>poudriere ports -c -F -f none -M /work/ports -p development</userinput>
For <application>Poudriere</application> version 3.1.20 and later: Para o <application>Poudriere</application> versão 3.1.20 e posterior:


New source string a year ago
Browse all component changes

Things to check

Unchanged translation

Source and translation are identical



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

Source information

Source string comment
(itstool) path: tip/screen
Source string location
String age
a year ago
Source string age
a year ago
Translation file
books/pt_BR/porters-handbook.po, string 4022