You can customize your build by providing local versions of
make.conf
and/or
src.conf
,
named
and
${arch}
/${branch}
/builds/${buildid}
/make.conf.server
,
respectively. These will be used in lieu of the default-named
files on the server side.${arch}
/${branch}
/builds/${buildid}
/src.conf.server
Similarly, if you wish to also affect the client-side
make.conf
, you may use
.
${arch}
/${branch}
/builds/${buildid}
/make.conf.client
Due to the fact that individual clients may each have
their own per-host make.conf
, the
contents of
will be appended to that
${arch}
/${branch}
/builds/${buildid}
/make.conf.clientmake.conf
, not supplant it, as is done
for
.${arch}
/${branch}
/builds/${buildid}
/make.conf.server
There is no similar functionality for
(what effect would it have?).${arch}
/${branch}
/builds/${buildid}
/src.conf.client
make.conf.target
to test new default ruby
version(For this case, the contents are identical for both server and client.)
make.conf.target
for clang builds(For this case, the contents are also identical for both server and client.)
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>.