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) ;) 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? Thanks again in advance for any advice you can provide. Best Wishes - Peter -- [ http://www.plosh.net/ ] - "Earth Halted: Please reboot to continue" -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 188 bytes Desc: OpenPGP digital signature Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20060613/8f481bac/signature.pgp
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. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 250 bytes Desc: OpenPGP digital signature Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20060613/a1398ae0/signature.pgp
On Mon, Jun 12, 2006 at 10:18:00PM -0700, Peter Losher wrote:> 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>From my experience with playing with make release, you can do it.First build your packages with "make package" or "pkg_create" to get a package tarball. Then put the packages into your_path/release/R/cdrom/disc1 into a directory call "packages". Create the package directory structure, like packages/All, packages/your_package_category, ... After that, modify the INDEX file so it only contain your packages (plus dependencies). Then run mkisomages.sh to create your ISO.> 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?I don't think you can, but check the source to comfirm. That's all from memory, may contain rough edges, hope it helps anyway. Andrew