From owner-freebsd-current@FreeBSD.ORG Wed Sep 10 16:53:04 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4697016A4BF; Wed, 10 Sep 2003 16:53:04 -0700 (PDT) Received: from meitner.wh.uni-dortmund.de (meitner.wh.Uni-Dortmund.DE [129.217.129.133]) by mx1.FreeBSD.org (Postfix) with ESMTP id 785F843FE5; Wed, 10 Sep 2003 16:53:02 -0700 (PDT) (envelope-from michaelnottebrock@gmx.net) Received: from lofi.dyndns.org (pc2-105.intern.meitner [10.3.12.105]) by meitner.wh.uni-dortmund.de (Postfix) with ESMTP id 84C4D167615; Thu, 11 Sep 2003 01:53:01 +0200 (CEST) Received: from gmx.net (kiste.my.domain [192.168.8.4]) (authenticated bits=0) by lofi.dyndns.org (8.12.9/8.12.9) with ESMTP id h8ANqv26078734 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 11 Sep 2003 01:52:58 +0200 (CEST) (envelope-from michaelnottebrock@gmx.net) Message-ID: <3F5FB957.7040407@gmx.net> Date: Thu, 11 Sep 2003 01:52:55 +0200 From: Michael Nottebrock User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax) X-Accept-Language: en-us, en, de-de MIME-Version: 1.0 To: deischen@freebsd.org References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new cc: freebsd-current@freebsd.org Subject: Re: Quo vadis, -CURRENT? (recent changes to cc & compatibility) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Sep 2003 23:53:04 -0000 Daniel Eischen wrote: >>I feel that a FreeBSD that manages to break so many existing configure-scripts >>and build systems is degraded in usefulness. > > Please, this is -current. If you want less pain then stick > with -stable and you won't be annoyed by the -pthread removal. Perhaps I should make it clear that, personally, I'm NOT very much annoyed. I know my way around in ports@, I actually do know what -CURRENT means and I have no problem with using the ports-collection exclusively instead of quickly compiling my own stuff right there in my user-account. The problem is just that this -CURRENT is supposed to be -STABLE rather soon, as we all know (I think the RE status for HEAD is 'Semi-Frozen', too). There are many users out there with 5.1-Release installed which have at best only a very distant clue about the fact they're running an "early adopter's release" and they won't be upgrading to 4.9-R or 4.10-R when the time arrives. For someone coming from 5.0-R or 5.1-R, the new "necessary evil behaviour" of cc/c++, be it -pedantic or -pthread, will be totally unexpected. -- ,_, | Michael Nottebrock | lofi@freebsd.org (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org