FreeBSD ports which are currently marked broken

Mark Linimon linimon at lonesome.com
Fri Jun 22 02:54:02 UTC 2012


On Thu, Jun 21, 2012 at 01:10:47PM +0100, Kaya Saman wrote:
> Is this only for "Ports" which don't build or "Ports" which have other
> issues??

You'll have to consult each port to see its message, but the vast majority
are marked that way because the do not build properly, or deinstall properly,
on the package building cluster.  In general, if a port builds and deinstalls
cleanly, and only fails in certain circumstances, it will not be marked with
the BROKEN tag.

Here are a couple of useful URLs with which to look at the state of an
individual port, using www/apache22 as an example:

  http://www.freshports.org/www/apache22/
  http://portsmon.freebsd.org/portoverview.py?category=www&portname=apache22

Here is a URL for all the ports currently marked BROKEN (as evaluated on
i386-9):

  http://portsmon.freebsd.org/portsconcordanceforbroken.py

mcl


More information about the freebsd-ports mailing list