From owner-freebsd-ports@FreeBSD.ORG Thu Dec 4 23:26:53 2003 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5F98116A4CE for ; Thu, 4 Dec 2003 23:26:53 -0800 (PST) Received: from mail.soaustin.net (mail.soaustin.net [207.200.4.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id A72F443FEC for ; Thu, 4 Dec 2003 23:26:52 -0800 (PST) (envelope-from linimon@lonesome.com) Received: by mail.soaustin.net (Postfix, from userid 502) id 43B1514691; Fri, 5 Dec 2003 01:26:52 -0600 (CST) Date: Fri, 5 Dec 2003 01:26:52 -0600 (CST) From: Mark Linimon X-X-Sender: linimon@pancho To: Clement Laforet In-Reply-To: <20031205072917.3c3573c8.sheepkiller@cultdeadsheep.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: ports@FreeBSD.org cc: Mark Linimon Subject: Re: [DRAFT] ports contributor's guide X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 Dec 2003 07:26:53 -0000 One of the other ideas I have for this document is to emphasize that one of our most pressing needs right now is to get the ports tree in good shape on 5.x. Many of these problems are due to a few underlying changes in gcc, such as 'no more varargs.h, no more multiline constants unless you say that's really what you want, no more assuming "standard namespace" in c++ code', and so forth. The bento pages are are a really good way to see how common these kinds of bugs are. Really, by the time we branch a 5-STABLE, it would be very desireable to get 100 or 200 more ports either working with gcc3.3, or declared obsolete if they're abandonware. mcl