From owner-freebsd-arch@FreeBSD.ORG  Sat May  1 18:55:58 2004
Return-Path: <owner-freebsd-arch@FreeBSD.ORG>
Delivered-To: freebsd-arch@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 6A28F16A4CF
	for <arch@freebsd.org>; Sat,  1 May 2004 18:55:58 -0700 (PDT)
Received: from mail.cableone.net (scanmail2.cableone.net [24.116.0.122])
	by mx1.FreeBSD.org (Postfix) with ESMTP id D973943D2F
	for <arch@freebsd.org>; Sat,  1 May 2004 18:55:55 -0700 (PDT)
	(envelope-from kitbsdlist2@HotPOP.com)
Received: from vixen42. (unverified [24.119.123.61]) 
	by smail2.cableone.net (SurgeMail 1.5d2) with ESMTP id 5880808 
	for <arch@freebsd.org>; Sat, 01 May 2004 18:44:41 -0700
Date: Sat, 1 May 2004 18:53:28 -0500
From: Vulpes Velox <kitbsdlist2@HotPOP.com>
To: arch@freebsd.org
Message-Id: <20040501185328.74568cec@vixen42.>
X-Mailer: Sylpheed version 0.9.10claws (GTK+ 1.2.10; i386-portbld-freebsd4.9)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-Server: High Performance Mail Server - http://surgemail.com
Subject: determining pkg dependencies
X-BeenThere: freebsd-arch@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussion related to FreeBSD architecture
	<freebsd-arch.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-arch>,
	<mailto:freebsd-arch-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-arch>
List-Post: <mailto:freebsd-arch@freebsd.org>
List-Help: <mailto:freebsd-arch-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-arch>,
	<mailto:freebsd-arch-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 02 May 2004 01:55:58 -0000

Well hope I have the right list...

Any one know of a good info on determining pkg/port dependencies
and how to go about determining what order they need to be install in?

I've been kicking around putting together something a little like
portupgrade, using c++, but don't know ruby, which makes it hard to
figure out how portupgrade does that. :/