From owner-freebsd-current Thu Jun 6 1:54:27 2002 Delivered-To: freebsd-current@freebsd.org Received: from axl.seasidesoftware.co.za (axl.seasidesoftware.co.za [196.31.7.201]) by hub.freebsd.org (Postfix) with ESMTP id 5CE7F37B408 for ; Thu, 6 Jun 2002 01:54:23 -0700 (PDT) Received: from sheldonh (helo=axl.seasidesoftware.co.za) by axl.seasidesoftware.co.za with local-esmtp (Exim 3.36 #1) id 17Ft27-0000QF-00; Thu, 06 Jun 2002 10:54:15 +0200 From: Sheldon Hearn To: Christopher Nehren Cc: current@freebsd.org Subject: Re: "Safe" to go to -CURRENT? In-reply-to: Your message of "05 Jun 2002 08:46:59 GMT." <1023266819.500.6.camel@prophecy.dyndns.org> Date: Thu, 06 Jun 2002 10:54:15 +0200 Message-ID: <1626.1023353655@axl.seasidesoftware.co.za> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 05 Jun 2002 08:46:59 GMT, Christopher Nehren wrote: > I've been monitoring the -CURRENT mailing list for about a day or two, > and haven't seen anything that's really broken (except for GCC 3.x, > which I don't use anyway). So, is it "safe" to upgrade to -CURRENT yet? > TIA for the info, > Chris There are still issues with the C++ compiler in the base system that make building X and some other C++ ports tricky. If you use a lot of X applications, you might want to hold back if you're looking for a smooth ride. The base system itself seems pretty stable, though. Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message