From owner-freebsd-ports@FreeBSD.ORG Fri Jun 24 07:13:40 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (unknown [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5C87F1065673 for ; Fri, 24 Jun 2011 07:13:40 +0000 (UTC) (envelope-from fullermd@over-yonder.net) Received: from thyme.infocus-llc.com (server.infocus-llc.com [206.156.254.44]) by mx1.freebsd.org (Postfix) with ESMTP id 32EDF8FC1B for ; Fri, 24 Jun 2011 07:13:39 +0000 (UTC) Received: from draco.over-yonder.net (c-174-50-4-38.hsd1.ms.comcast.net [174.50.4.38]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by thyme.infocus-llc.com (Postfix) with ESMTPSA id 12E2837B56E; Fri, 24 Jun 2011 02:13:39 -0500 (CDT) Received: by draco.over-yonder.net (Postfix, from userid 100) id 6583661C42; Fri, 24 Jun 2011 02:13:38 -0500 (CDT) Date: Fri, 24 Jun 2011 02:13:38 -0500 From: "Matthew D. Fuller" To: Kurt Jaeger Message-ID: <20110624071338.GJ89895@over-yonder.net> References: <4E034711.6030007@webrz.net> <4E03470D.7040909@yandex.ru> <20110623162920.GE16648@home.opsec.eu> <20110624092457.7d82744e@gmail.com> <20110624070900.GF16648@home.opsec.eu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20110624070900.GF16648@home.opsec.eu> X-Editor: vi X-OS: FreeBSD User-Agent: Mutt/1.5.21-fullermd.4 (2010-09-15) X-Virus-Scanned: clamav-milter 0.97.1 at thyme.infocus-llc.com X-Virus-Status: Clean Cc: freebsd-ports@freebsd.org Subject: Re: Spamassassin vs Perl 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: Fri, 24 Jun 2011 07:13:40 -0000 On Fri, Jun 24, 2011 at 09:09:00AM +0200 I heard the voice of Kurt Jaeger, and lo! it spake thus: > > How can one reconstruct a good dependency tree of all perl related > ports which allows to cleanly rebuild them all ? I always just start with `portupgrade -f p5-\*`. Then look around in the old site_perl dir for stragglers (usually fairly few). Of course, that won't catch non-modules that depend tightly on the version, but those are rare enough that I've always just dealt with them when they came to notice. -- Matthew Fuller (MF4839) | fullermd@over-yonder.net Systems/Network Administrator | http://www.over-yonder.net/~fullermd/ On the Internet, nobody can hear you scream.