From owner-freebsd-hackers@FreeBSD.ORG Thu Sep 2 20:07:09 2004 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6350916A4CF for ; Thu, 2 Sep 2004 20:07:09 +0000 (GMT) Received: from ds.netgate.net (ds.netgate.net [205.214.170.232]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2290443D49 for ; Thu, 2 Sep 2004 20:07:09 +0000 (GMT) (envelope-from ctodd@chrismiller.com) Received: (qmail 23554 invoked from network); 2 Sep 2004 20:07:08 -0000 Received: from vp4.netgate.net (ibrew@205.214.170.248) by ds.netgate.net with SMTP; 2 Sep 2004 20:07:08 -0000 Date: Thu, 2 Sep 2004 13:07:08 -0700 (PDT) From: ctodd@chrismiller.com X-X-Sender: ibrew@vp4.netgate.net To: John Baldwin In-Reply-To: <200409021538.26944.jhb@FreeBSD.org> Message-ID: References: <200409021538.26944.jhb@FreeBSD.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-hackers@FreeBSD.org Subject: Re: How to customize a release? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Sep 2004 20:07:09 -0000 John, Thanks for the quick reply. > There is a 'KERNELS' variable that is helpful. I see this in the Makefile, but if I were to use KERNELS=MYKERNEL will that prevent the other standard kernels from being built? > Also, look at LOCAL_PATCHES and LOCAL_SCRIPTS as far as how to patch a > release build. Note that you can include patches to > src/release/Makefile in LOCAL_PATCHES if need be. :) LOCAL_PATCHES is what I'm using now (waiting for build to finish to see how it worked). I was hoping for a way to populate the src tree without doing a full release so I could create the patches, then run make release only once (it took 5 hours on my devel system last time). At this point I've already done that, but for the next time I'd like to work more efficiently. BTW, I see I overlooked the RELEASENOUPDATE variable in the man page, so that answers my question about preventing CVS updates on "make rerelease". Unfortunately make rerelease didn't rebuild anything in /R/stage (I got "ftp.1 is up to date"). Am I supposed to delete the stage directories to force a rebuild, or do I need to do a full release to incorporate any minor changes? Chris