Source string Read only

(itstool) path: listitem/para
Context English State
<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>:
<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"/>.
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.
Using Sets
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.
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:
<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:
From this list, <application>Poudriere</application> <citerefentry><refentrytitle>nullfs</refentrytitle><manvolnum>5</manvolnum></citerefentry>-mounts the <emphasis>first existing</emphasis> directory tree into the <filename>/var/db/ports</filename> directory of the build jails. Hence, all custom options are used for all the ports during this run of <command>testport</command>.
After the directory structure for a set is provided, the options for a particular port can be altered. For example:
<prompt>#</prompt> <userinput>poudriere options -c www/firefox -z devset</userinput>
The configuration dialog for <package role="port">www/firefox</package> is shown, and options can be edited. The selected options are saved to the <literal>devset</literal> set.
<application>Poudriere</application> is very flexible in the option configuration. They can be set for particular jails, ports trees, and for multiple ports by one command. Refer to <citerefentry vendor="ports"><refentrytitle>poudriere</refentrytitle><manvolnum>8</manvolnum></citerefentry> for details.
Providing a Custom <filename>make.conf</filename> File
Similar to using sets, <application>Poudriere</application> will also use a custom <filename>make.conf</filename> if it is provided. No special command line argument is necessary. Instead, <application>Poudriere</application> looks for existing files matching a name scheme derived from the command line. For instance:
causes <application>Poudriere</application> to check for the existence of these files in this order:


User avatar None

New source string

FreeBSD Doc / books_porters-handbookEnglish

New source string 7 months ago
Browse all component changes


English English
No related strings found in the glossary.

Source information

Source string comment
(itstool) path: listitem/para
Source string location
String age
7 months ago
Source string age
7 months ago
Translation file
books/porters-handbook.pot, string 4069