From owner-freebsd-current Wed May 2 15:49: 0 2001 Delivered-To: freebsd-current@freebsd.org Received: from meow.osd.bsdi.com (meow.osd.bsdi.com [204.216.28.88]) by hub.freebsd.org (Postfix) with ESMTP id D522D37B423 for ; Wed, 2 May 2001 15:48:56 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by meow.osd.bsdi.com (8.11.2/8.11.2) with ESMTP id f42MmhG48763; Wed, 2 May 2001 15:48:43 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20010502154108Q.jkh@osd.bsdi.com> Date: Wed, 02 May 2001 15:48:01 -0700 (PDT) From: John Baldwin To: Jordan Hubbard Subject: Re: PATCH: partial fix for broken "make release"... Cc: current@FreeBSD.org, tlambert@primenet.com Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 02-May-01 Jordan Hubbard wrote: > From: Terry Lambert > Subject: PATCH: partial fix for broken "make release"... > Date: Wed, 2 May 2001 22:00:37 +0000 (GMT) > >> The "make release" stuff is broken, at least in 4.3, and possibly >> before that. >> >> There are several obviously broken things: >> >> o The libssh stuff is not installed, and it is not built > > That would be a failure in make world, not make release. He probably doesn't have src-crypto or cvs-crypto in his cvsup file. *shrug* Works fine here and worked fine for the 4.3 release build. >> o The files jade_1.2.1-13.diff.gz and pdf_sec.ps are not >> available from any of the listed mirros in the "ports" > > That would be a failure in the ports collection, not make release. Yes. Haven't seen this locally though, but I may have these files prefetched to /usr/docdistfiles on the local snap building machine. >> o If you set KERNCONF to a non-default value ("GENERIC" is >> the default value), then sysinstall can't find it to > > I'm not clear as to why you'd want to? GENERIC is the best kernel for > creating generally useable releases, but I imagine you have some other > reason for chosing a specific configuration for which I also expect > you're copying the config file into ${CHROOTDIR}/usr/src/sys/${ARCH}/conf > from somewhere else? I can't see how this change by itself makes what > appears to be the desired functionality a reality. You could use LOCAL_PATCHES to do it if your patch created a new config file. This would be appropriate if you were rolling an internal release using your own kernel config. In that case his patches make sense. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message