From owner-freebsd-ports@FreeBSD.ORG  Sun Feb 27 03:43:56 2011
Return-Path: <owner-freebsd-ports@FreeBSD.ORG>
Delivered-To: freebsd-ports@freebsd.org
Received: from mx2.freebsd.org (mx2.freebsd.org [IPv6:2001:4f8:fff6::35])
	by hub.freebsd.org (Postfix) with ESMTP id D2163106566B
	for <freebsd-ports@freebsd.org>; Sun, 27 Feb 2011 03:43:56 +0000 (UTC)
	(envelope-from dougb@FreeBSD.org)
Received: from doug-optiplex.ka9q.net (hub.freebsd.org
	[IPv6:2001:4f8:fff6::36])
	by mx2.freebsd.org (Postfix) with ESMTP id 5323E14D8DA;
	Sun, 27 Feb 2011 03:43:50 +0000 (UTC)
Message-ID: <4D69C875.4010304@FreeBSD.org>
Date: Sat, 26 Feb 2011 19:43:49 -0800
From: Doug Barton <dougb@FreeBSD.org>
Organization: http://SupersetSolutions.com/
User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US;
	rv:1.9.2.13) Gecko/20110129 Thunderbird/3.1.7
MIME-Version: 1.0
To: Sergio de Almeida Lenzi <lenzi.sergio@gmail.com>
References: <4D690CA4.9090008@gmail.com>
	<1298738086.92768.3.camel@z6000.lenzicasa>
In-Reply-To: <1298738086.92768.3.camel@z6000.lenzicasa>
X-Enigmail-Version: 1.1.2
OpenPGP: id=1A1ABC84
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: David Demelier <demelier.david@gmail.com>, freebsd-ports@freebsd.org
Subject: Re: Find a corrupt port
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: Sun, 27 Feb 2011 03:43:57 -0000

On 02/26/2011 08:34, Sergio de Almeida Lenzi wrote:
> I use this script to get rid of the problem
> the script detects @pkgdep record without argument
> and deletes it from the +CONTENTS file in the /var/db/pkg/* directory
> ===========================================
>
> for i in /var/db/pkg/*/+CONTENTS
> do
> 	if grep -q "@pkgdep $" $i
> 	then
> 		sed -i "" -e "/@pkgdep $/d" $i
> 		echo nullpkg in $i
> 	fi
> done

The problem with this is that dependencies are actually recorded as a 
pair. For example:

@pkgdep pkg-config-0.25_1
@comment DEPORIGIN:devel/pkg-config

Someone else already was kind enough to mention 'portmaster 
--check-depends' which will prompt you to do the right thing and/or 
notify you about ports that you need to reinstall.


hth,

Doug

-- 

	Nothin' ever doesn't change, but nothin' changes much.
			-- OK Go

	Breadth of IT experience, and depth of knowledge in the DNS.
	Yours for the right price.  :)  http://SupersetSolutions.com/