When building packages for a release, it may be
necessary to manually update the ports
and src
trees to the release tag and use
-novcs
and
-noportsvcs
.
To build package sets intended for use on a CD-ROM,
use the -cdrom
option to
dopackages
.
If the disk space is not available on the cluster, use
-nodistfiles
to avoid collecting distfiles.
After the initial build completes, restart the build
with
-restart -fetch-original
to collect updated distfiles as well. Then, once the
build is post-processed, take an inventory of the list
of files fetched:
%
cd ${arch}
/${branch}
%
find distfiles > distfiles-${release}
You should use that output to periodically clean out
the distfiles from ftp-master
. When space
gets tight, distfiles from recent releases can be kept while
others can be thrown away.
Once the distfiles have been uploaded (see below),
the final release package set must be created. Just to be
on the safe side, run the
script by hand to make sure all the CD-ROM restricted packages
and distfiles have been pruned. Then, copy the
${arch}
/${branch}
/cdrom.sh
directory to
${arch}
/${branch}
/packages
.
Once the packages are safely moved off, contact the Release Engineering Team ${arch}
/${branch}
/packages-${release}
<re@FreeBSD.org>
and inform them of the release package location.
Remember to coordinate with the Release Engineering Team <re@FreeBSD.org>
about the timing
and status of the release builds.
This, and other documents, can be downloaded from http://ftp.FreeBSD.org/pub/FreeBSD/doc/
For questions about FreeBSD, read the
documentation before
contacting <questions@FreeBSD.org>.
For questions about this documentation, e-mail <doc@FreeBSD.org>.