From owner-freebsd-current Tue Sep 3 11:57:07 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA18685 for current-outgoing; Tue, 3 Sep 1996 11:57:07 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id LAA18680 for ; Tue, 3 Sep 1996 11:57:02 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id LAA04805; Tue, 3 Sep 1996 11:55:21 -0700 From: Terry Lambert Message-Id: <199609031855.LAA04805@phaeton.artisoft.com> Subject: Re: Latest Current build failure To: smpatel@umiacs.umd.edu (Sujal Patel) Date: Tue, 3 Sep 1996 11:55:21 -0700 (MST) Cc: jkh@time.cdrom.com, current@freebsd.org In-Reply-To: from "Sujal Patel" at Sep 2, 96 11:11:38 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > On Mon, 2 Sep 1996, Jordan K. Hubbard wrote: > > > > I haven't seen any real solutions to the buildable-current problem. > > > > Actually, I've been proposing a solution for close to 2 years now, > > we've just never actually set about the process of implementing it. > > Perhaps it's just me, but I really don't expect current to build all the > time. It's just a fact of life... That's why it's called -current. > > If you really need something that's in -current, then just wait for the > 2.2 SNAPS, they are fairly regular. So make up a name somewhere between "-current" and "2.2 SNAPS", with the primary criteria being that you expect it to build all the time. Then we can complain about that. 8-). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers.