From owner-freebsd-current Mon Feb 12 14: 9:17 2001 Delivered-To: freebsd-current@freebsd.org Received: from mta6.snfc21.pbi.net (mta6.snfc21.pbi.net [206.13.28.240]) by hub.freebsd.org (Postfix) with ESMTP id 475D837B491 for ; Mon, 12 Feb 2001 14:09:15 -0800 (PST) Received: from zippy.pacbell.net ([207.214.149.181]) by mta6.snfc21.pbi.net (Sun Internet Mail Server sims.3.5.2000.01.05.12.18.p9) with ESMTP id <0G8N00824YUA05@mta6.snfc21.pbi.net> for current@freebsd.org; Mon, 12 Feb 2001 13:39:47 -0800 (PST) Received: by zippy.pacbell.net (Postfix, from userid 1000) id EBB7617CA; Mon, 12 Feb 2001 13:42:27 -0800 (PST) Date: Mon, 12 Feb 2001 13:42:16 -0800 From: Alex Zepeda Subject: Re: -CURRENT is bad for me... In-reply-to: <200102122119.f1CLJaW31538@harmony.village.org>; from imp@harmony.village.org on Mon, Feb 12, 2001 at 02:19:36PM -0700 To: Warner Losh Message-id: <20010212134216.A1647@zippy.mybox.zip> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-disposition: inline User-Agent: Mutt/1.2.5i References: <200102122119.f1CLJaW31538@harmony.village.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Feb 12, 2001 at 02:19:36PM -0700, Warner Losh wrote: > Changes of this magnitude require a bump of the major number, even > though we've already done that in -current. It breaks nearly > everything, including the upgrade path. Alternatively, the locking > changes need to be backed out. Yup, I agree here. IMO so many things depend on the stdio bits, that a major number increase would have been desireable. So far, bzip2, pine/pico, GNU make, the GNU i18n stuff, fetchmail all needed to be rebuilt. Bumping the major number would at least allow these a stay of execution. - alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message