From owner-freebsd-ports@FreeBSD.ORG Wed Mar 26 08:51:18 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 AD086106564A for ; Wed, 26 Mar 2008 08:51:18 +0000 (UTC) (envelope-from picard@kti.ae.poznan.pl) Received: from newton.kti.ae.poznan.pl (newton.kti.ae.poznan.pl [150.254.204.44]) by mx1.freebsd.org (Postfix) with ESMTP id 6B4B48FC40 for ; Wed, 26 Mar 2008 08:51:18 +0000 (UTC) (envelope-from picard@kti.ae.poznan.pl) Received: from copernic.kti.ae.poznan.pl ([150.254.204.47]) by newton.kti.ae.poznan.pl with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69 (FreeBSD)) (envelope-from ) id 1JeRLh-0007pv-NA; Wed, 26 Mar 2008 09:51:09 +0100 Received: from picard by copernic.kti.ae.poznan.pl with local (Exim 4.69 (FreeBSD)) (envelope-from ) id 1JeRL9-000KHT-Tm; Wed, 26 Mar 2008 09:50:36 +0100 Date: Wed, 26 Mar 2008 09:50:35 +0100 From: Willy Picard To: Doug Barton Message-ID: <20080326085035.GA1756@copernic.kti.ae.poznan.pl> References: <20080325212146.GA32955@copernic.kti.ae.poznan.pl> <47E97F0F.10900@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <47E97F0F.10900@FreeBSD.org> User-Agent: Mutt/1.5.17 (2007-11-01) Sender: Willy Picard 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 08:51:18 -0000 On Tue, Mar 25, 2008 at 03:39:11PM -0700, Doug Barton wrote: > Willy Picard wrote: >> I would like to know if there is a smart way to ask portmaster to ignore BROKEN >> ports. Currently I added a +IGNOREME file to all BROKEN ports I have but I would >> like portmaster to automatically ignore these ports without the +IGNOREME file. > > Sorry, portmaster hasn't developed psychic abilities yet, so it can't know > for sure what you want to do with your broken ports vs. what all the other > portmaster users want to do with them. :) Well, I am not thinking about paranormal abilities for portmaster, I was rather thinking about a nice option (e.g. --ignore-broken) that would allow postmaster to ignore BROKEN ports during a "postmaster -a". Currently, I have the www/flock port installed. This port is marked as BROKEN (not by me, so this is not "my broken port" but "a broken port"). When I run "postmaster -a", postmaster exists before updating of ports because flock is broken. I therefore add a +IGNOREME file in the /var/db/pkg/flock-* dir. However, if the flock port is not marked BROKEN tomorrow, I will have to 1) detect this fact, 2) remove the +IGNOREME file. 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. Best regards, Willy Picard -- Willy Picard e-mail: picard@kti.ae.poznan.pl Dept. of Information Technology www: http://www.kti.ae.poznan.pl/ The Poznan University of Economics tel: +48 61 848 05 49 Mansfelda 4, 60-854 Poznan, Poland fax: +48 61 848 38 40