From owner-freebsd-current Mon Jan 29 14:46:09 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id OAA17206 for current-outgoing; Mon, 29 Jan 1996 14:46:09 -0800 (PST) Received: from time.cdrom.com (time.cdrom.com [192.216.222.226]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id OAA17195 for ; Mon, 29 Jan 1996 14:46:02 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.6.12/8.6.9) with SMTP id OAA12032; Mon, 29 Jan 1996 14:45:44 -0800 To: Nate Williams cc: current@FreeBSD.org Subject: Re: I'm rather annoyed with -current. In-reply-to: Your message of "Mon, 29 Jan 1996 08:56:51 MST." <199601291556.IAA08024@rocky.sri.MT.net> Date: Mon, 29 Jan 1996 14:45:43 -0800 Message-ID: <12030.822955543@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@FreeBSD.org Precedence: bulk > Both of these problems are due to ordering problems in the Makefile, > which can be fixed in the 'world' target, but don't really fit into the > current model used. Ah. Feh, this REALLY needs to be fixed. -current is broken right now, plain and simple, and if the people who implemented the features which have added all this dependency brokenness don't stand up and finish the job soon, I think it might be reasonable to start calling for the backing-out of certain changes, the thread stuff coming especially to mind. Leaving -current broken for this long is truly not acceptable and it's persisted for long enough. > It basically boils down to the fact that we *should* be building the > sources out of the src tree and not out of the stuff in > /usr/{lib|include} etc... (Which I've argued against in the past as > un-necessary and complex, but I think we've now reached critical mass > and require it.) I agree. Do I hear a volunteer? :-) > > I haven't been able to build -stable for several weeks now - is it Ack, typo, I meant -current. Jordan