NAME

SYNOPSIS

DESCRIPTION

See the FLAVORS section in poudriere(8) for supported flavors syntax.

See the CUSTOMIZATION section in poudriere(8) to learn how to build binary packages with options that differ from defaults.

poudriere will disable make jobs for packages not listed in ALLOW_MAKE_JOBS_PACKAGES, unless ALLOW_MAKE_JOBS is set in poudriere.conf. The number of jobs can be controlled in make.conf with the ports(7) flags MAKE_JOBS_NUMBER and MAKE_JOBS_NUMBER_LIMIT. Beware that there is no global job control so each builder created from -J (or the default PARALLEL_JOBS) will spawn as many jobs as the ports framework allows.

SUBCOMMANDS

-a

Build all ports in the tree with all flavors.

-f file

Build ports listed in the file.

The path to the file has to be absolute. Ports must be specified in the form of “category/port” and sh(1)-style comments are allowed. Multiple -f file arguments may be specified at once.

OPTIONS

-B name

Specify which buildname to use. By default YYYY-MM-DD_HH:MM:SS will be used. This can be used to resume a previous build and use the same log and URL paths. Resuming a build will not retry built/failed/skipped/ignored packages.

-C

Clean only the packages specified on the command line or in the file given by -f file. Implies -c for -a.

-c

Clean all previously built packages and logs.

-F

Fetch only from the original MASTER_SITES. Skip FreeBSD mirrors.

-i

Interactive mode.

Open an interactive shell session in the jail after the build is done and before the clean-up. It is a convenient way to do some additional testing.

A local pkg.conf(5) repository configuration will be installed to ${LOCALBASE}/etc/pkg/repos/local.conf so that pkg(8) can be used with any existing packages built for the jail. The default FreeBSD repository will be disabled by default.

-j name

Run the bulk build on the jail named name.

-J maxjobs[:prebuildmaxjobs]

Specify the number of jobs that will run in parallel for a bulk build. The optional second parameter, prebuildmaxjobs, is the number of jobs used for the steps before the build, they are more IO bound than CPU bound, so you may want to use a different number. The default pre-build value is 1.25 times the value of the build value.

-I

Advanced interactive mode.

Leave the jail running with ports installed after building and testing. It is a convenient way to do some additional testing. See poudriere-jail(8) to learn how to stop a running poudriere jail.

Similarly to -i, the -I flag will cause pkg.conf(5) to be installed in the jail.

-k

Do not consider failures to be fatal when using -t. Do not skip dependent ports on findings. This flag is automatically set when using -at.

-N

Do not build a package repository when the build is completed.

-n

Dry run. Show what would be done, but do not actually build or delete any packages.

-p tree

Specify on which ports tree the bulk build will be done.

-R

Clean RESTRICTED packages after building.

-r

Recursively test all dependencies as well. This flag is automatically set when using -at.

-S

Do not recursively rebuild packages affected by other packages requiring incremental rebuild. This may result in broken packages if the ones they depend on are updated, are not ABI-compatible, and were not properly PORTREVISION bumped.

-T

Try building BROKEN ports by defining TRYBROKEN for the build.

-t

Add some testing to the specified ports. Add -r to recursively test all port dependencies as well. When used with -a then -rk are implied.

-v

Enable additional information to be shown during the build. Specify twice to enable debug output.

-w

Save WRKDIR on build failure. The WRKDIR will be tarred up into ${POUDRIERE_DATA}/wrkdirs.

-z set

This specifies which SET to use for the build. See the CUSTOMIZATION section in poudriere(8) for examples of how this is used.

EXAMPLES

Example 1: Starting a Bulk Build

The following example starts a bulk build of two ports.

#
 poudriere bulk accessibility/sct www/firefox

    

SEE ALSO

AUTHORS