From owner-freebsd-ports@FreeBSD.ORG  Fri Jun 22 02:54:02 2012
Return-Path: <owner-freebsd-ports@FreeBSD.ORG>
Delivered-To: ports@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 87868106564A;
	Fri, 22 Jun 2012 02:54:02 +0000 (UTC)
	(envelope-from linimon@lonesome.com)
Received: from mail.soaustin.net (pancho.soaustin.net [76.74.250.40])
	by mx1.freebsd.org (Postfix) with ESMTP id 6470A8FC15;
	Fri, 22 Jun 2012 02:54:02 +0000 (UTC)
Received: by mail.soaustin.net (Postfix, from userid 502)
	id 0DEC85620B; Thu, 21 Jun 2012 21:54:02 -0500 (CDT)
Date: Thu, 21 Jun 2012 21:54:02 -0500
From: Mark Linimon <linimon@lonesome.com>
To: Kaya Saman <kayasaman@gmail.com>
Message-ID: <20120622025402.GB2608@lonesome.com>
References: <201206210828.q5L8SrdL078006@portsmonj.FreeBSD.org>
	<201206211201.q5LC1a5k099714@fire.js.berklix.net>
	<CAPj0R5KXivo=d7RDPm7i+MuxUB8uh753k6LQDL45=Q6+222qmQ@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CAPj0R5KXivo=d7RDPm7i+MuxUB8uh753k6LQDL45=Q6+222qmQ@mail.gmail.com>
User-Agent: Mutt/1.5.20 (2009-06-14)
Cc: ports@freebsd.org, "Julian H. Stacey" <jhs@berklix.com>,
	portmgr-feedback@freebsd.org
Subject: Re: FreeBSD ports which are currently marked broken
X-BeenThere: freebsd-ports@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Porting software to FreeBSD <freebsd-ports.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
	<mailto:freebsd-ports-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports>
List-Post: <mailto:freebsd-ports@freebsd.org>
List-Help: <mailto:freebsd-ports-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
	<mailto:freebsd-ports-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Jun 2012 02:54:02 -0000

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