Date: Tue, 13 Jun 2006 10:34:38 -0700 From: "Bruce A. Mah" <bmah@freebsd.org> To: Peter Losher <plosher-keyword-freebsd.a36e57@plosh.net> Cc: freebsd-stable@freebsd.org Subject: Re: 'make release' questions... Message-ID: <448EF72E.6090004@freebsd.org> In-Reply-To: <448E4A88.2000102@plosh.net> References: <448E4A88.2000102@plosh.net>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigC9178B497013D11BB7030CD7 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable If memory serves me right, Peter Losher wrote: > I have been mucking about w/ 'make release' for some time now (strippin= g > out OpenSSH, sendmail, Heimdal, bits oF BIND, etc.) and while I now hav= e > a working .iso image, that will install and update, I have some > questions that 'man release' just won't answer. :) >=20 > First, is there any way to instruct 'make release' to just build certai= n > 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 o= f > 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. --------------enigC9178B497013D11BB7030CD7 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFEjvcu2MoxcVugUsMRAqOLAJ9bqeLm3nfdOvqkdT4CG45f67S64ACfY7ID /y5PDWptcxjjtsuTOXOaTxY= =QimP -----END PGP SIGNATURE----- --------------enigC9178B497013D11BB7030CD7--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?448EF72E.6090004>