From owner-freebsd-arch Fri Mar 16 16:45: 0 2001 Delivered-To: freebsd-arch@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 664) id B710C37B719; Fri, 16 Mar 2001 16:44:57 -0800 (PST) Date: Fri, 16 Mar 2001 16:44:57 -0800 From: David O'Brien To: Jordan Hubbard Cc: bright@wintelcom.net, arch@FreeBSD.ORG Subject: Re: NO MORE '-BETA' Message-ID: <20010316164457.A57253@hub.freebsd.org> Reply-To: arch@freebsd.org References: <20010316134349.K29888@fw.wintelcom.net> <20010316163748Z.jkh@osd.bsdi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010316163748Z.jkh@osd.bsdi.com>; from jkh@osd.bsdi.com on Fri, Mar 16, 2001 at 04:37:48PM -0800 X-Operating-System: FreeBSD 4.2-STABLE Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Mar 16, 2001 at 04:37:48PM -0800, Jordan Hubbard wrote: > I'll also expect that the ports folks will simply bump the bento > cluster "artificially" up to 4.4-RELEASE by setting the versions there > manually, so the packages will all bear the correct information. 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. A ports committer under the above conditions have to see in the bento error logs there was a configure problem, guess at the fix (since it isn't as easy to test on their own box), commit a fix, wait 24-36 hours later to see if indeed the commit fixed the problem, repeat if needed... -- -- David (obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message