4 Starting the Build

The scripts/dopackages* scripts are used to perform the builds. Most useful are:

• dopackages.5 - Perform a 5.X build

• dopackages.5-exp - Perform a 5.X build with experimental patches (5-exp branch)

• dopackages.6 - Perform a 6.X build

• dopackages.6-exp - Perform a 6.X build with experimental patches (6-exp branch)

• dopackages.7 - Perform a 7.X build

• dopackages.7-exp - Perform a 7.X build with experimental patches (7-exp branch)

• dopackages.8 - Perform a 8.X build

These are wrappers around dopackages, and are all symlinked to dopackages.wrapper. New branch wrapper scripts can be created by symlinking dopackages.${branch} to dopackages.wrapper. These scripts take a number of arguments. For example:

dopackages.6 ${arch} [-options]

[-options] may be zero or more of the following:

• -nofinish - Do not perform post-processing once the build is complete. Useful if you expect that the build will need to be restarted once it finishes. This option should always be used for normal build operations.

• -finish - Perform post-processing only.

• -restart - Restart an interrupted (or non-finished) build from the beginning. Ports that failed on the previous build will be rebuilt.

• -continue - Restart an interrupted (or non-finished) build. Will not rebuild ports that failed on the previous build.

• -incremental - Compare the interesting fields of the new INDEX with the previous one, remove packages and log files for the old ports that have changed, and rebuild the rest. This cuts down on build times substantially since unchanged ports do not get rebuilt every time.

• -cdrom - This package build is intended to end up on a CD-ROM, so NO_CDROM packages and distfiles should be deleted in post-processing.

• -nobuild - Perform all the preprocessing steps, but do not actually do the package build.

• -noindex - Do not rebuild INDEX during preprocessing.

• -noduds - Do not rebuild the duds file (ports that are never built, e.g. those marked IGNORE, NO_PACKAGE, etc.) during preprocessing.

• -trybroken - Try to build BROKEN ports (off by default because the amd64/i386™ clusters are fast enough now that when doing incremental builds, more time was spent rebuilding things that were going to fail anyway. Conversely, the other clusters are slow enough that it would be a waste of time to try and build BROKEN ports).

• -nocvs - Do not cvs update the src tree during preprocessing.

• -noportscvs - Do not cvs update the ports tree during preprocessing.

• -norestr - Do not attempt to build RESTRICTED ports.

• -plistcheck - Make it fatal for ports to leave behind files after deinstallation.

• -distfiles - Collect distfiles that pass make checksum for later uploading to ftp-master. Use this sparingly because it takes up a lot of disk space. You should remove the distfiles once they have been transfered to ftp-master.

• -fetch-original - Fetch the distfile from the original MASTER_SITES rather than ftp-master.

If the last build finished cleanly you do not need to delete anything; if it was interrupted you just need to run dosetupnodes on all clients for the the relevant branch. errors/, logs/, packages/, and so forth, are cleaned by the scripts. If you are short of space, you can also clean out ports/distfiles/. Leave the latest/ directory alone; it is a symlink for the webserver.

Make sure the ${arch} build is run as the ports-${arch} user or it will complain loudly.

Be careful that ports/Makefile does not specify any empty subdirectories. This is especially important if you are doing an -exp build. If the build process encounters an empty subdirectory, both package build phases will stop short, and an error similar to the following will be written to ${arch}/${branch}/make.[0|1]:

don't know how to make dns-all(continuing)

To correct this problem, simply comment out or remove the SUBDIR entries that point to empty subdirectories. After doing this, you can restart the build by running the proper dopackages command with the -restart option.