From owner-freebsd-ports@FreeBSD.ORG Mon Feb 20 20:42:44 2006 Return-Path: X-Original-To: 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 5640316A420 for ; Mon, 20 Feb 2006 20:42:44 +0000 (GMT) (envelope-from hans@lambermont.dyndns.org) Received: from lambermont.dyndns.org (lambermont.dyndns.org [82.93.47.245]) by mx1.FreeBSD.org (Postfix) with ESMTP id 75BAF43D58 for ; Mon, 20 Feb 2006 20:42:43 +0000 (GMT) (envelope-from hans@lambermont.dyndns.org) Received: by lambermont.dyndns.org (Postfix, from userid 1001) id 2278F14DA98; Mon, 20 Feb 2006 21:42:42 +0100 (CET) Date: Mon, 20 Feb 2006 21:42:42 +0100 To: freebsd-ports@freebsd.org Message-ID: <20060220204242.GD31008@leia.lambermont.dyndns.org> References: <43BCF31F.8050900@FreeBSD.org> <20060214213514.GB20841@leia.lambermont.dyndns.org> <20060219143913.GA868@weller-fahy.com> <20060219145045.GB868@weller-fahy.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060219145045.GB868@weller-fahy.com> User-Agent: Mutt/1.4.2.1i From: hans@lambermont.dyndns.org (Hans Lambermont) Subject: Re: portmaster [was: New /bin/sh based script to manage 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: Mon, 20 Feb 2006 20:42:44 -0000 David J. Weller-Fahy wrote: > David J. Weller-Fahy wrote: >> Hrm... would something like the attached script be sufficient? it >> outputs a tree-like view of what will be updated. It's not very >> complex, and doesn't take into account things like removing ports >> already ouput from any future output, but it works for me. > > Which apparently didn't get through, here's an inline version: ... Nice work ! The output grows very quicky with the missing hash-like filter. Here's a snippet of the well over 1000 lines of output I get : :::::::::::>pkgconfig-0.17.2::pkgconfig-0.20 :::::::::::::>gettext-0.14.5::gettext-0.14.5_1 ::::::::::::::>libtool-1.5.20::libtool-1.5.22_1 :::::::::::::::>libtool-1.5.20::libtool-1.5.22_1 :::::::::::::>libtool-1.5.20::libtool-1.5.22_1 ::::::::::::::>libtool-1.5.20::libtool-1.5.22_1 ::::::::::::>libtool-1.5.20::libtool-1.5.22_1 ::::::::::::>gettext-0.14.5::gettext-0.14.5_1 Is there a way to implement a perl-like hash filter in sh land to clean this up ? As a next step to such a filter I would suggest to reverse the dependency output, so that the build order gets shown. What do you think of this ? regards, Hans Lambermont