Date: Sun, 22 Jul 2007 01:53:06 -0500 From: linimon@lonesome.com (Mark Linimon) To: Peter Jeremy <peterjeremy@optushome.com.au> Cc: ports@FreeBSD.org Subject: Re: Ports depending on FORBIDDEN ports Message-ID: <20070722065306.GF4336@soaustin.net> In-Reply-To: <20070721005252.GJ1176@turion.vk2pj.dyndns.org> References: <20070721005252.GJ1176@turion.vk2pj.dyndns.org>
next in thread | previous in thread | raw e-mail | index | archive | help
I'm actually doing a slight superset by looking at dependent ports of (ignore/broken/forbidden/failed) ports, now that I have updated the graph and can "see" it better. It sounds like people are already working on the misc/compat3x dependents. Most of these ports are antiques. IMHO sysutils/eject should be fixed; there is a PR for it already: 112754. We definitely need to find someone who will keep zope up to date. I have privately emailed both the maintainer and the submitter of the last N PRs. There are a few other Python ports marked NO_PACKAGE, and I have also emailed the maintainers. This affects about 80 packages. Fixing all of these would add over 100 packages to the pointyhat builds. Thanks for taking a look at all of these. mcl
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070722065306.GF4336>