Date: Tue, 3 Mar 2009 07:54:03 -0600 From: Mark Linimon <linimon@lonesome.com> To: "Andrew W. Nosenko" <andrew.w.nosenko@gmail.com> Cc: Garrett Cooper <yanefbsd@gmail.com>, freebsd-ports@freebsd.org, Paul Schmehl <pschmehl_lists@tx.rr.com> Subject: Re: Dead projects in ports tree Message-ID: <20090303135403.GB23268@lonesome.com> In-Reply-To: <6161f3180903030140q40098f89nfbdf2ed94f5e677f@mail.gmail.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>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20090303135403.GB23268>