2. FreeBSD Doc
  3. books_porters-handbook
  4. Portuguese (Brazil)
  5. Translate

Translation

(itstool) path: sect2/para
After the build completes, and regardless of whether it was successful, a shell is provided within the jail. The shell is used to investigate further. <application>Poudriere</application> can be told to leave the jail running after the build finishes with <option>-I</option>. <application>Poudriere</application> will show the command to run when the jail is no longer needed. It is then possible to <citerefentry><refentrytitle>jexec</refentrytitle><manvolnum>8</manvolnum></citerefentry> into it:
558/4990
Context English Portuguese (Brazil) State
The dash or <literal>null</literal> in the <literal>METHOD</literal> column means that <application>Poudriere</application> will not update or change this ports tree, ever. It is completely up to the user to maintain this tree, including all local modifications that may be used for testing new ports and submitting patches. O traço ou <literal>null</literal> na coluna <literal>METHOD</literal> significa que o <application>Poudriere</application> nunca irá atualizar ou alterar esta árvore de ports. É de responsabilidade total do usuário a manutenção desta árvore, incluindo todas as modificações locais que podem ser usadas para testar novos ports e enviar patches.
Keeping Poudriere Ports Trees Updated Mantendo as Árvores de Ports do Poudriere Atualizadas
As straightforward as with jails described earlier: Tão simples quanto com as jails descritas anteriormente:
<prompt>#</prompt> <userinput>poudriere ports -u -p <replaceable>PORTSTREE</replaceable></userinput> <prompt>#</prompt> <userinput>poudriere ports -u -p <replaceable>PORTSTREE</replaceable></userinput>
Will update the given <replaceable>PORTSTREE</replaceable>, one tree given by the output of <command>poudriere -l</command>, to the latest revision available on the official servers. Vai atualizar a <replaceable>PORTSTREE</replaceable>, uma árvore dada pela saída de <command>poudriere -l</command>, para a última revisão disponível nos servidores oficiais.
Ports trees without a method, see <xref linkend="testing-poudriere-ports-tree-manual"/>, cannot be updated like this. They must be updated manually by the porter. As arvores de ports sem um método, veja <xref linkend="testing-poudriere-ports-tree-manual"/>, não podem ser atualizadas assim. Elas devem ser atualizadas manualmente pelo mantenedor de ports.
Testing Ports Testando Ports
After jails and ports trees have been set up, the result of a contributor's modifications to the ports tree can be tested. Depois que as jails e as árvores de ports foram configuradas, o resultado das modificações de um colaborador na árvore de ports pode ser testado.
For example, local modifications to the <package role="port">www/firefox</package> port located in <filename>/work/ports/www/firefox</filename> can be tested in the previously created 11.3-RELEASE jail: Por exemplo, modificações locais no port <package role="port">www/firefox</package> localizado em <filename>/work/ports/www/firefox</filename> pode ser testado na jail 11.3-RELEASE criada anteriormente:
<prompt>#</prompt> <userinput>poudriere testport -j 113Ramd64 -p development -o www/firefox</userinput> <prompt>#</prompt> <userinput>poudriere testport -j 113Ramd64 -p development -o www/firefox</userinput>
This will build all dependencies of <application>Firefox</application>. If a dependency has been built previously and is still up-to-date, the pre-built package is installed. If a dependency has no up-to-date package, one will be built with default options in a jail. Then <application>Firefox</application> itself is built. Isso irá compilar todas as dependências do <application>firefox</application>. Se uma dependência foi criada anteriormente e ainda está atualizada, o pacote pré-criado é instalado. Se uma dependência não tiver um pacote atualizado, ela será compilada com opções padrão em uma jail. Depois disso o <application>firefox</application> será compilado.
The complete build of every port is logged to <filename>/poudriere/data/logs/bulk/113Ri386-development/<replaceable>build-time</replaceable>/logs</filename>. A compilação completa de cada port será registrada em <filename>/poudriere/data/logs/bulk/113Ri386-development/<replaceable>build-time</replaceable>/logs</filename>.
The directory name <literal>113Ri386-development</literal> is derived from the arguments to <literal>-j</literal> and <literal>-p</literal>, respectively. For convenience, a symbolic link <filename>/poudriere/data/logs/bulk/113Ri386-development/latest</filename> is also maintained. The link points to the latest <replaceable>build-time</replaceable> directory. Also in this directory is an <filename>index.html</filename> for observing the build process with a web browser. O nome do diretório <literal>113Ri386-development</literal> é derivado dos argumentos para <literal>-j</literal> e <literal>-p</literal>, respectivamente. Por conveniência, um link simbólico <filename>/poudriere/data/logs/bulk/113Ri386-development/latest</filename> também é mantido. O link aponta para o mais recente diretório <replaceable>build-time</replaceable>. Neste diretório também se encontra um <filename>index.html</filename> para que possa ser possível observar o processo de compilação com um navegador web.
By default, <application>Poudriere</application> cleans up the jails and leaves log files in the directories mentioned above. To ease investigation, jails can be kept running after the build by adding <option>-i</option> to <command>testport</command>: Por padrão, o <application>Poudriere</application> limpa as jails e deixa os arquivos de log nos diretórios mencionados acima. Para facilitar a investigação, as jails podem ser mantidas em execução após a compilação, adicionando a opção <option>-i</option> ao <command>testport</command>:
<prompt>#</prompt> <userinput>poudriere testport -j 113Ramd64 -p development -i -o www/firefox</userinput> <prompt>#</prompt> <userinput>poudriere testport -j 113Ramd64 -p development -i -o www/firefox</userinput>
After the build completes, and regardless of whether it was successful, a shell is provided within the jail. The shell is used to investigate further. <application>Poudriere</application> can be told to leave the jail running after the build finishes with <option>-I</option>. <application>Poudriere</application> will show the command to run when the jail is no longer needed. It is then possible to <citerefentry><refentrytitle>jexec</refentrytitle><manvolnum>8</manvolnum></citerefentry> into it: Depois que a compilação é concluída, e independentemente de ter sido bem-sucedida, um shell é fornecido dentro da jail. O shell é usado para investigações adicionais. O <application>Poudriere</application> pode ser dito para deixar a jail em execução após a conclusão da compilação com <option>-i</option>. O <application>Poudriere</application> mostrará o comando para ser executado quando a jail não for mais necessária. E então é possível fazer um <citerefentry><refentrytitle>jexec</refentrytitle><manvolnum>8</manvolnum></citerefentry> para dentro dele:
<prompt>#</prompt> <userinput>poudriere testport -j 113Ramd64 -p development -I -o www/firefox</userinput>
[...]
====&gt;&gt; Installing local Pkg repository to /usr/local/etc/pkg/repos
====&gt;&gt; Leaving jail 113Ramd64-development-n running, mounted at /poudriere/data/.m/113Ramd64-development/ref for interactive run testing
====&gt;&gt; To enter jail: jexec 113Ramd64-development-n env -i TERM=$TERM /usr/bin/login -fp root
====&gt;&gt; To stop jail: poudriere jail -k -j 113Ramd64 -p development
<prompt>#</prompt> <userinput>jexec 113Ramd64-development-n env -i TERM=$TERM /usr/bin/login -fp root</userinput>
<prompt>#</prompt> <userinput><replaceable>[do some stuff in the jail]</replaceable></userinput>
<prompt>#</prompt> <userinput>exit</userinput>
<prompt>#</prompt> <userinput>poudriere jail -k -j 113Ramd64 -p development</userinput>
====&gt;&gt; Umounting file systems 		<prompt>#</prompt> <userinput>poudriere testport -j 113Ramd64 -p development -I -o www/firefox</userinput>
[...]
====&gt;&gt; Installing local Pkg repository to /usr/local/etc/pkg/repos
====&gt;&gt; Leaving jail 113Ramd64-development-n running, mounted at /poudriere/data/.m/113Ramd64-development/ref for interactive run testing
====&gt;&gt; To enter jail: jexec 113Ramd64-development-n env -i TERM=$TERM /usr/bin/login -fp root
====&gt;&gt; To stop jail: poudriere jail -k -j 113Ramd64 -p development
<prompt>#</prompt> <userinput>jexec 113Ramd64-development-n env -i TERM=$TERM /usr/bin/login -fp root</userinput>
<prompt>#</prompt> <userinput><replaceable>[do some stuff in the jail]</replaceable></userinput>
<prompt>#</prompt> <userinput>exit</userinput>
<prompt>#</prompt> <userinput>poudriere jail -k -j 113Ramd64 -p development</userinput>
====&gt;&gt; Umounting file systems
An integral part of the FreeBSD ports build infrastructure is the ability to tweak ports to personal preferences with options. These can be tested with <application>Poudriere</application> as well. Adding the <option>-c</option>: Uma parte integral da infraestrutura de compilação de ports do FreeBSD é a capacidade de ajustar os ports as preferências pessoais por meio de opções. Elas podem ser testadas com o <application>Poudriere</application> também. Adicionando a opção <option>-c</option>:
<prompt>#</prompt> <userinput>poudriere testport -c -o www/firefox</userinput> <prompt>#</prompt> <userinput>poudriere testport -c -o www/firefox</userinput>
Presents the port configuration dialog before the port is built. The ports given after <option>-o</option> in the format <literal><replaceable>category</replaceable>/<replaceable>portname</replaceable></literal> will use the specified options, all dependencies will use the default options. Testing dependent ports with non-default options can be accomplished using sets, see <xref linkend="testing-poudriere-sets"/>. Apresenta o diálogo de configuração do port antes que o port seja compilado. Os ports informados após o <option>-o</option> no formato <literal><replaceable>category</replaceable>/<replaceable>portname</replaceable></literal> usará as opções especificadas, todas as dependências usarão as opções padrão. O teste de ports dependentes com opções não padrão pode ser realizado usando conjuntos, consulte <xref linkend="testing-poudriere-sets"/>.
When testing ports where <filename>pkg-plist</filename> is altered during build depending on the selected options, it is recommended to perform a test run with all options selected <emphasis>and</emphasis> one with all options deselected. Ao testar ports nos quais o <filename>pkg-plist</filename> é alterado durante a compilação, dependendo das opções selecionadas, é recomendável executar um teste com todas as opções selecionadas <emphasis>e</emphasis> um com todas as opções desmarcadas.
Using Sets Usando Conjuntos
For all actions involving builds, a so-called <emphasis>set</emphasis> can be specified using <literal>-z <replaceable>setname</replaceable></literal>. A set refers to a fully independent build. This allows, for instance, usage of <command>testport</command> with non-standard options for the dependent ports. Para todas as ações envolvendo builds, um então chamado <emphasis>conjunto</emphasis> pode ser especificado usando <literal>-z <replaceable>setname</replaceable></literal>. Um conjunto se refere a uma compilação totalmente independente. Isso permite, por exemplo, o uso de <command>testport</command> com opções não padrão para os ports dependentes.
To use sets, <application>Poudriere</application> expects an existing directory structure similar to <varname>PORT_DBDIR</varname>, defaults to <filename>/var/db/ports</filename> in its configuration directory. This directory is then <citerefentry><refentrytitle>nullfs</refentrytitle><manvolnum>5</manvolnum></citerefentry>-mounted into the jails where the ports and their dependencies are built. Usually a suitable starting point can be obtained by recursively copying the existing <varname>PORT_DBDIR</varname> to <filename>/usr/local/etc/poudriere.d/<replaceable>jailname</replaceable>-<replaceable>portname</replaceable>-<replaceable>setname</replaceable>-options</filename>. This is described in detail in <citerefentry vendor="ports"><refentrytitle>poudriere</refentrytitle><manvolnum>8</manvolnum></citerefentry>. For instance, testing <package role="port">www/firefox</package> in a specific set named <literal>devset</literal>, add the <literal>-z devset</literal> parameter to the testport command: Para usar sets, o <application>Poudriere</application> espera uma estrutura de diretórios existente semelhante a <varname>PORT_DBDIR</varname>, o padrão é <filename>/var/db/ports</filename> no seu diretório de configuração. Este diretório é então <citerefentry><refentrytitle>nullfs</refentrytitle><manvolnum>5</manvolnum></citerefentry>-montado nas jails onde os ports e suas dependências são compilados. Normalmente, um ponto de partida adequado pode ser obtido copiando de forma recursiva o <varname>PORT_DBDIR</varname> para <filename>/usr/local/etc/poudriere.d/<replaceable>jailname</replaceable>-<replaceable>portname</replaceable>-<replaceable>setname</replaceable>-options</filename>. Isso é descrito em detalhes em <citerefentry vendor="ports"><refentrytitle>poudriere</refentrytitle><manvolnum>8</manvolnum></citerefentry>. Por exemplo, para testar o <package role="port">www/firefox</package> em um conjunto específico chamado <literal>devset</literal>, adicione o parâmetro <literal>-z devset</literal> ao comando testport:
<prompt>#</prompt> <userinput>poudriere testport -j 113Ramd64 -p development -z devset -o www/firefox</userinput> <prompt>#</prompt> <userinput>poudriere testport -j 113Ramd64 -p development -z devset -o www/firefox</userinput>
This will look for the existence of these directories in this order: Isso irá procurar pela existência desses diretórios nesta ordem:
<filename>/usr/local/etc/poudriere.d/113Ramd64-development-devset-options</filename> <filename>/usr/local/etc/poudriere.d/113Ramd64-development-devset-options</filename>
<filename>/usr/local/etc/poudriere.d/113Ramd64-devset-options</filename> <filename>/usr/local/etc/poudriere.d/113Ramd64-devset-options</filename>
<filename>/usr/local/etc/poudriere.d/113Ramd64-development-options</filename> <filename>/usr/local/etc/poudriere.d/113Ramd64-development-options</filename>
<filename>/usr/local/etc/poudriere.d/devset-options</filename> <filename>/usr/local/etc/poudriere.d/devset-options</filename>
<filename>/usr/local/etc/poudriere.d/development-options</filename> <filename>/usr/local/etc/poudriere.d/development-options</filename>

Loading…

User avatar None

New source string

FreeBSD Doc / books_porters-handbook — Portuguese (Brazil)

New source string a year ago
Browse all component changes

Glossary

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

Source information

Source string comment
(itstool) path: sect2/para
Source string location
book.translate.xml:19421
String age
a year ago
Source string age
a year ago
Translation file
books/pt_BR/porters-handbook.po, string 4056