From owner-freebsd-ports@FreeBSD.ORG Tue Mar 3 13:54:04 2009 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 67CBA1065692 for ; Tue, 3 Mar 2009 13:54:04 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: from mail.soaustin.net (lefty.soaustin.net [66.135.55.46]) by mx1.freebsd.org (Postfix) with ESMTP id 441048FC19 for ; Tue, 3 Mar 2009 13:54:04 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: by mail.soaustin.net (Postfix, from userid 502) id D218B8C06F; Tue, 3 Mar 2009 07:54:03 -0600 (CST) Date: Tue, 3 Mar 2009 07:54:03 -0600 From: Mark Linimon To: "Andrew W. Nosenko" Message-ID: <20090303135403.GB23268@lonesome.com> References: <7d6fde3d0902281509v6a98521as618421daf52b3abe@mail.gmail.com> <7d6fde3d0902281605u2a251513q44ccfc0c8226c9fd@mail.gmail.com> <20090302223600.GD29616@redundancy.redundancy.org> <5282E09CCA57B5914BF69048@utd65257.utdallas.edu> <7d6fde3d0903030026s7cd80ac5ia2e596d94c6dbba6@mail.gmail.com> <6161f3180903030140q40098f89nfbdf2ed94f5e677f@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <6161f3180903030140q40098f89nfbdf2ed94f5e677f@mail.gmail.com> User-Agent: Mutt/1.5.18 (2008-05-17) Cc: Garrett Cooper , freebsd-ports@freebsd.org, Paul Schmehl Subject: Re: Dead projects in ports tree X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Mar 2009 13:54:05 -0000 On Tue, Mar 03, 2009 at 11:40:42AM +0200, Andrew W. Nosenko wrote: > Frankly, I would glad to see absolutely another discussion: not about > dropping software that works (and as far as I understand, which port > is maintained), but about making needed but broken software work again > (e.g. valgrind, which is compiliable, but absolutelly not runnable > since freebsd-7.0, and unfortunatelly has no replacement...) Well, it all depends on how much work volunteers are willing to do. fwiw, I periodically send out email about broken ports (as evaluated on i386-current): http://docs.freebsd.org/cgi/mid.cgi?20090126081726.DBA671CC6F A less verbose, but constantly updated, version is at http://portsmon.freebsd.org/portsconcordanceforbroken.py . It's showing 165 ports ATM, a few with PRs to fix them. mcl