From owner-freebsd-current  Mon Sep  2 20:11:59 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id UAA27832
          for current-outgoing; Mon, 2 Sep 1996 20:11:59 -0700 (PDT)
Received: from mickey.umiacs.umd.edu (mickey.umiacs.umd.edu [128.8.120.49])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id UAA27825
          for <current@FreeBSD.org>; Mon, 2 Sep 1996 20:11:56 -0700 (PDT)
Received: (smpatel@localhost)
	by mickey.umiacs.umd.edu (8.7.5/UMIACS-0.9/04-05-88)
	id XAA04539; Mon, 2 Sep 1996 23:11:38 -0400 (EDT)
Date: Mon, 2 Sep 1996 23:11:38 -0400 (EDT)
From: Sujal Patel <smpatel@umiacs.umd.edu>
To: "Jordan K. Hubbard" <jkh@time.cdrom.com>
cc: current@FreeBSD.org
Subject: Re: Latest Current build failure 
In-Reply-To: <6665.841718171@time.cdrom.com>
Message-ID: <Pine.OSF.3.91.960902230945.9398B-100000@mickey.umiacs.umd.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
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.


Sujal