From owner-freebsd-ports@FreeBSD.ORG  Tue May 18 05:38:59 2004
Return-Path: <owner-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 CF78E16A4CF
	for <ports@freebsd.org>; Tue, 18 May 2004 05:38:59 -0700 (PDT)
Received: from woozle.rinet.ru (woozle.rinet.ru [195.54.192.68])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 5468F43D91
	for <ports@freebsd.org>; Tue, 18 May 2004 05:36:58 -0700 (PDT)
	(envelope-from marck@rinet.ru)
Received: from localhost (localhost [127.0.0.1])
	by woozle.rinet.ru (8.12.11/8.12.11) with ESMTP id i4IBjFDK053971
	for <ports@freebsd.org>; Tue, 18 May 2004 15:45:16 +0400 (MSD)
	(envelope-from marck@rinet.ru)
Date: Tue, 18 May 2004 15:45:15 +0400 (MSD)
From: Dmitry Morozovsky <marck@rinet.ru>
To: ports@freebsd.org
Message-ID: <20040518152749.M52881@woozle.rinet.ru>
X-NCC-RegID: ru.rinet
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Subject: ports subtree dependencies checking
X-BeenThere: freebsd-ports@freebsd.org
X-Mailman-Version: 2.1.1
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: Tue, 18 May 2004 12:38:59 -0000

Dear colleagues,

as all of you knows, keeping up to date thw whole ports tree involves
tremendous number of disk operation per cvs/cvsup. So, I use small script to
keep up-to date rather small set of ports (less than 1000, comparing to 10k+
total ports in the tree).

Sometimes this leads to broken dependencies (e.g., when tracked port becomes
dependent on some new port, or when dependency port moves). The latter case
partially can be covered by tracking MOVED file, the former can not.

Previously, `make index' would complaint about missing dependencies, so these
ports can be caught. Now, with INDEX_JOBS parallel index building, these errors
are hidden in the process.

Looking through Mk/bsd.port.mk (scaring process, BTW ;-) does not enlight me
enough.

Any suggestions?

Please keep me CC:d as I'm not subscribed to ports@

Thanks in advance.


Sincerely,
D.Marck                                     [DM5020, MCK-RIPE, DM3-RIPN]
------------------------------------------------------------------------
*** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- marck@rinet.ru ***
------------------------------------------------------------------------