From owner-freebsd-arch Fri Mar 16 18:15: 9 2001 Delivered-To: freebsd-arch@freebsd.org Received: from meow.osd.bsdi.com (meow.osd.bsdi.com [204.216.28.88]) by hub.freebsd.org (Postfix) with ESMTP id 6031837B719 for ; Fri, 16 Mar 2001 18:15:04 -0800 (PST) (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 f2H2EEG73189; Fri, 16 Mar 2001 18:14:14 -0800 (PST) (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: <20010316173503T.jkh@osd.bsdi.com> Date: Fri, 16 Mar 2001 18:14:29 -0800 (PST) From: John Baldwin To: Jordan Hubbard Subject: Re: NO MORE '-BETA' Cc: bright@wintelcom.net, arch@FreeBSD.org Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 17-Mar-01 Jordan Hubbard wrote: >> This doesn't solve the ports problem as ports maintainers cannot use >> bento for their own build testing. To take this approach puts us back in >> the FORTRAN, punched cards, batch days. > > Sure they can, they can either just brute-force set the release string > on their own machines as well or, since this is hardly rocket science, > they can use the mechanisms already provided. From bsd.port.subdir.mk: > > .if !defined(OSREL) > OSREL!= /usr/bin/uname -r | sed -e 's/[-(].*//' > .endif > .if !defined(OSVERSION) > .if exists(/sbin/sysctl) > OSVERSION!= /sbin/sysctl -n kern.osreldate > .else > OSVERSION!= /usr/sbin/sysctl -n kern.osreldate > .endif > > As you can see, both OSREL and OSVERSION can be set in /etc/make.conf > or the command line to override the default setting. Actually, the biggest problem in the past has been configure scripts which call uname directly and try to parse the output, so setting OSREL or OSVERSION doesn't help at all there. :) For that you need to tweak newvers.sh in your own kernel. Plus, you need to do it for your the ports cluster so it can run through the ports generating error logs people can look at and try to get fixes in before the final build is done. Just committing it to the tree is a rather simple way of achieving all of this. It would be nice to also know how many people are confused vs. how many people _aren't_ confused. If 2% of our -stable userbase doesn't get it, then I'm not sure that is justification for axeing it. This is even documented and announced on the lists for crying out loud. :) -- 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-arch" in the body of the message