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

Source string Read only

(itstool) path: sect1/para
Context English State
Options and dependencies for the specified ports are configured:
<prompt>#</prompt> <userinput>poudriere options -j <replaceable>11amd64</replaceable> -p <replaceable>local</replaceable> -z <replaceable>workstation</replaceable> -f <replaceable>11amd64-local-workstation-pkglist</replaceable></userinput>
Finally, packages are built and a package repository is created:
<prompt>#</prompt> <userinput>poudriere bulk -j <replaceable>11amd64</replaceable> -p <replaceable>local</replaceable> -z <replaceable>workstation</replaceable> -f <replaceable>11amd64-local-workstation-pkglist</replaceable></userinput>
While running, pressing <keycombo action="simul"><keycap>Ctrl</keycap><keycap>t</keycap></keycombo> displays the current state of the build. <application>Poudriere</application> also builds files in <filename>/poudriere/logs/bulk/<replaceable>jailname</replaceable></filename> that can be used with a web server to display build information.
After completion, the new packages are now available for installation from the <application>poudriere</application> repository.
For more information on using <application>poudriere</application>, see <citerefentry vendor="ports"><refentrytitle>poudriere</refentrytitle><manvolnum>8</manvolnum></citerefentry> and the main web site, <link xlink:href=""/>.
Configuring pkg Clients to Use a Poudriere Repository
While it is possible to use both a custom repository along side of the official repository, sometimes it is useful to disable the official repository. This is done by creating a configuration file that overrides and disables the official configuration file. Create <filename>/usr/local/etc/pkg/repos/FreeBSD.conf</filename> that contains the following:
FreeBSD: {
enabled: no
Usually it is easiest to serve a poudriere repository to the client machines via HTTP. Set up a webserver to serve up the package directory, for instance: <filename>/usr/local/poudriere/data/packages/<replaceable>11amd64</replaceable></filename>, where <filename><replaceable>11amd64</replaceable></filename> is the name of the build.
If the URL to the package repository is: <literal></literal>, then the repository configuration file in <filename>/usr/local/etc/pkg/repos/custom.conf</filename> would look like:
custom: {
url: "<replaceable></replaceable>",
enabled: yes,
Post-Installation Considerations
Regardless of whether the software was installed from a binary package or port, most third-party applications require some level of configuration after installation. The following commands and locations can be used to help determine what was installed with the application.
Most applications install at least one default configuration file in <filename>/usr/local/etc</filename>. In cases where an application has a large number of configuration files, a subdirectory will be created to hold them. Often, sample configuration files are installed which end with a suffix such as <filename>.sample</filename>. The configuration files should be reviewed and possibly edited to meet the system's needs. To edit a sample file, first copy it without the <filename>.sample</filename> extension.
Applications which provide documentation will install it into <filename>/usr/local/share/doc</filename> and many applications also install manual pages. This documentation should be consulted before continuing.
Some applications run services which must be added to <filename>/etc/rc.conf</filename> before starting the application. These applications usually install a startup script in <filename>/usr/local/etc/rc.d</filename>. See <link linkend="configtuning-starting-services">Starting Services</link> for more information.
By design, applications do not run their startup script upon installation, nor do they run their stop script upon deinstallation or upgrade. This decision is left to the individual system administrator.
Users of <citerefentry><refentrytitle>csh</refentrytitle><manvolnum>1</manvolnum></citerefentry> should run <command>rehash</command> to rebuild the known binary list in the shells <envar>PATH</envar>.
Use <command>pkg info</command> to determine which files, man pages, and binaries were installed with the application.
Dealing with Broken Ports
When a port does not build or install, try the following:
Search to see if there is a fix pending for the port in the <link xlink:href="@@URL_RELPREFIX@@/support.html">Problem Report database</link>. If so, implementing the proposed fix may fix the issue.
Ask the maintainer of the port for help. Type <command>make maintainer</command> in the ports skeleton or read the port's <filename>Makefile</filename> to find the maintainer's email address. Remember to include the <literal>$FreeBSD:</literal> line from the port's <filename>Makefile</filename> and the output leading up to the error in the email to the maintainer.
Some ports are not maintained by an individual but instead by a group maintainer represented by a <link xlink:href="@@URL_RELPREFIX@@/doc/en_US.ISO8859-1/articles/mailing-list-faq/article.html">mailing list</link>. Many, but not all, of these addresses look like <email role="nolink">freebsd-<replaceable>listname</replaceable></email>. Please take this into account when sending an email.
In particular, ports maintained by <email role="nolink"></email> are not maintained by a specific individual. Instead, any fixes and support come from the general community who subscribe to that mailing list. More volunteers are always needed!
If there is no response to the email, use Bugzilla to submit a bug report using the instructions in <link xlink:href="@@URL_RELPREFIX@@/doc/en_US.ISO8859-1/articles/problem-reports/article.html">Writing FreeBSD Problem Reports</link>.
Fix it! The <link xlink:href="@@URL_RELPREFIX@@/doc/en_US.ISO8859-1/books/porters-handbook/index.html">Porter's Handbook</link> includes detailed information on the ports infrastructure so that you can fix the occasional broken port or even submit your own!
Install the package instead of the port using the instructions in <xref linkend="pkgng-intro"/>.


No matching activity found.

Browse all component changes

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
books/handbook.pot, string 1825