From owner-freebsd-current Fri Jun 7 1:34:23 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 1E2F737B406; Fri, 7 Jun 2002 01:34:17 -0700 (PDT) Received: from sheldonh (helo=axl.seasidesoftware.co.za) by axl.seasidesoftware.co.za with local-esmtp (Exim 3.36 #1) id 17GFCq-00096O-00; Fri, 07 Jun 2002 10:34:48 +0200 From: Sheldon Hearn To: obrien@freebsd.org Cc: Christopher Nehren , current@freebsd.org Subject: Re: "Safe" to go to -CURRENT? In-reply-to: Your message of "Thu, 06 Jun 2002 10:14:52 MST." <20020606101452.F59829@dragon.nuxi.com> Date: Fri, 07 Jun 2002 10:34:48 +0200 Message-ID: <34991.1023438888@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 Thu, 06 Jun 2002 10:14:52 MST, "David O'Brien" wrote: > > There are still issues with the C++ compiler in the base system that > > make building X and some other C++ ports tricky. > > There is no issue with the C++ compiler. There is issue with the X > source that uses depreciated features. The fact remains, desktop-environment users looking for an easy ride should not be jumping on the -CURRENT wagon bus just now. Such people probably don't really care "whose fault it is". But thanks for clarifying. I'll be sure to explain more carefully to the next person who asks me whether now's a good time for -CURRENT. :-) Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message