From owner-freebsd-ports@FreeBSD.ORG  Mon Sep 26 10:24:01 2005
Return-Path: <owner-freebsd-ports@FreeBSD.ORG>
X-Original-To: freebsd-ports@freebsd.org
Delivered-To: freebsd-ports@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 2C76016A41F;
	Mon, 26 Sep 2005 10:24:01 +0000 (GMT) (envelope-from sem@FreeBSD.org)
Received: from relay-er5.mbrd.ru (relay-er5.mbrd.ru [194.117.71.33])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 487AE43D4C;
	Mon, 26 Sep 2005 10:24:00 +0000 (GMT) (envelope-from sem@FreeBSD.org)
Received: from msd.mbrd.ru ([172.16.4.9])
	by relay-er5.mbrd.ru with esmtp (Exim 4.x)
	id 1EJq95-000H9A-Sk; Mon, 26 Sep 2005 14:23:39 +0400
Message-ID: <4337CC2C.2020202@FreeBSD.org>
Date: Mon, 26 Sep 2005 14:23:40 +0400
From: Sergey Matveychuk <sem@FreeBSD.org>
User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "Michael C. Shultz" <ringworm01@gmail.com>
References: <200509251559.53576.ringworm01@gmail.com>
In-Reply-To: <200509251559.53576.ringworm01@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: freebsd-ports@freebsd.org, portmgr@freebsd.org
Subject: Re: ports/Mk/bsd.port.mk,v 1.517 2005/09/15 12:24:33 question
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: Mon, 26 Sep 2005 10:24:01 -0000

Michael C. Shultz wrote:
> Is it possible/desirable to modify bsd.port.mk so that
> ports marked IGNORE or BROKEN exit with an error
> code, like "make check-conflicts" does if there is a conflict?
> 
> Right now there is a problem with sysutils/portmanager
> not properly handling ports marked BROKEN because
> make seems to exit with no error.  I could add parsing 
> Makefiles for the term "BROKEN" to portmanager, but that
> seems a shame, because untill now portmanager has never
> needed to snoop the insides of Makefiles.

It's an old issue. ports/63216 is under portmgr wish.

-- 
Sem.