From owner-freebsd-ports@FreeBSD.ORG  Sat Nov 23 20:35:25 2013
Return-Path: <owner-freebsd-ports@FreeBSD.ORG>
Delivered-To: freebsd-ports@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 36721F55
 for <freebsd-ports@freebsd.org>; Sat, 23 Nov 2013 20:35:25 +0000 (UTC)
Received: from outgoing.tristatelogic.com (segfault.tristatelogic.com
 [69.62.255.118]) by mx1.freebsd.org (Postfix) with ESMTP id 1A65429CC
 for <freebsd-ports@freebsd.org>; Sat, 23 Nov 2013 20:35:24 +0000 (UTC)
Received: from segfault-nmh-helo.tristatelogic.com (localhost [127.0.0.1])
 by segfault.tristatelogic.com (Postfix) with ESMTP id 7A8DF3ACC0
 for <freebsd-ports@freebsd.org>; Sat, 23 Nov 2013 12:35:24 -0800 (PST)
From: "Ronald F. Guilmette" <rfg@tristatelogic.com>
To: freebsd-ports@freebsd.org
Subject: Graphing installed ports
Date: Sat, 23 Nov 2013 12:35:24 -0800
Message-ID: <43125.1385238924@server1.tristatelogic.com>
X-BeenThere: freebsd-ports@freebsd.org
X-Mailman-Version: 2.1.16
Precedence: list
List-Id: Porting software to FreeBSD <freebsd-ports.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/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: Sat, 23 Nov 2013 20:35:25 -0000


Has anyone ever used a graphing tool (such as GraphViz) to create a
graph of all of the installed ports on a given system and their
dependencies?

I think that this would be interesting... and perhaps even useful...
to do, but it seems like such an obvious idea that I have to
guess that somebody else has already coded up a small script to
do this exact thing.  If so, I see no reason why I should re-invent
this wheel.