From owner-freebsd-current@FreeBSD.ORG Fri Sep 19 23:14:13 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 8A69516A4B3 for ; Fri, 19 Sep 2003 23:14:13 -0700 (PDT) Received: from svr7.m-online.net (svr7.m-online.net [62.245.150.229]) by mx1.FreeBSD.org (Postfix) with ESMTP id D14BB43FE1 for ; Fri, 19 Sep 2003 23:14:12 -0700 (PDT) (envelope-from h@schmalzbauer.de) Received: from schmalzbauer.de (ppp-62-245-232-106.mnet-online.de [62.245.232.106]) by svr7.m-online.net (Postfix) with ESMTP id 63B3B7EA4B for ; Sat, 20 Sep 2003 08:14:10 +0200 (CEST) Message-ID: <3F6BF02F.9040707@schmalzbauer.de> Date: Sat, 20 Sep 2003 08:14:07 +0200 From: Harald Schmalzbauer User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.5b) Gecko/20030920 Thunderbird/0.2 X-Accept-Language: en-us, en MIME-Version: 1.0 To: current@freebsd.org Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: ports and -current 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: Sat, 20 Sep 2003 06:14:13 -0000 Well, for weeks now I couldn't compile (almost) any port. It seems that ports aren't tested against -current. Is that true? Not only the -pthread removement broke countless ports (some of them are easy to fix others aren't) also the entire new kde fails. Is there no aim to have ports running on -current? I'm asking because my "workstation" has enough resources to track -current to help testing. But if I breake ports with -current I won't keep tracking it. Thanks, -Harry