From owner-freebsd-ports@FreeBSD.ORG Wed Mar 26 22:28:56 2008 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9710B106568F for ; Wed, 26 Mar 2008 22:28:56 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from mail2.fluidhosting.com (mx21.fluidhosting.com [204.14.89.4]) by mx1.freebsd.org (Postfix) with SMTP id 30EE58FC18 for ; Wed, 26 Mar 2008 22:28:53 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: (qmail 4680 invoked by uid 399); 26 Mar 2008 22:31:14 -0000 Received: from localhost (HELO ?192.168.0.5?) (dougb@dougbarton.us@127.0.0.1) by localhost with ESMTP; 26 Mar 2008 22:31:14 -0000 X-Originating-IP: 127.0.0.1 Message-ID: <47EACD31.2070803@FreeBSD.org> Date: Wed, 26 Mar 2008 15:24:49 -0700 From: Doug Barton Organization: http://www.FreeBSD.org/ User-Agent: Thunderbird 2.0.0.12 (Windows/20080213) MIME-Version: 1.0 To: Willy Picard References: <20080325212146.GA32955@copernic.kti.ae.poznan.pl> <47E97F0F.10900@FreeBSD.org> <20080326085035.GA1756@copernic.kti.ae.poznan.pl> In-Reply-To: <20080326085035.GA1756@copernic.kti.ae.poznan.pl> X-Enigmail-Version: 0.95.6 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-ports@freebsd.org Subject: Re: portmaster and BROKEN ports X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Mar 2008 22:28:58 -0000 Willy Picard wrote: > portupgrade simply ignores BROKEN ports during a "portupgrade -a". I am not even > asking about a similar behaviour for portmaster. I wanted just to ask if an > option allows to do the same. If no such an option exists, I think that its > addition to the functionality of portmaster may be worth considering. I think it's important for users to know when their ports go into a BROKEN state, so ignoring them is not an option. If a user actually wants to ignore a port that is BROKEN, the +IGNOREME mechanism is available, as you pointed out. Doug -- This .signature sanitized for your protection