If memory serves me right, Peter Losher wrote: > I have been mucking about w/ 'make release' for some time now (stripping > out OpenSSH, sendmail, Heimdal, bits oF BIND, etc.) and while I now have > a working .iso image, that will install and update, I have some > questions that 'man release' just won't answer. :) > > First, is there any way to instruct 'make release' to just build certain > packages (and their dependencies) for inclusion in the release instead > of a blanket NOPORTS? There's no need for us spend two/three days > compiling all the various ports when we will only use a small handful of > them on most of our boxes. (and would speed up the amount of time it > takes to roll out a new release) ;)
NOPORTS controls whether or not the ports tree gets checked and built for the release. It doesn't do a full package build. If release-building speed is really important for you, you might want to turn on NODOC. This avoids building a doc toolchain (i.e. the textproc/docproj port), the doc/ tree, and the release documentation. I haven't read through src/release/Makefile for awhile, so I'm not sure if there's an easy way to build (and include) the selected packages build you want. I know we don't do this for official release builds...all the packages get built on the ports-building cluster and get added afterwards. You might want to read through src/release/Makefile...it might take a few passes but it'll probably be worth your time just so you can understand all the various steps going on. Just a thought. > Second, is there a way to build/tell sysinstall that if NO_OPENSSH is > set, that it doesn't ask you whether you want to enable SSH logins? <speculation>I don't think so.</speculation> Bruce.
signature.asc
Description: OpenPGP digital signature