From owner-freebsd-ports-bugs@FreeBSD.ORG  Sat Mar 30 19:50:03 2013
Return-Path: <owner-freebsd-ports-bugs@FreeBSD.ORG>
Delivered-To: freebsd-ports-bugs@smarthost.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115])
 by hub.freebsd.org (Postfix) with ESMTP id BF5D5724
 for <freebsd-ports-bugs@smarthost.ysv.freebsd.org>;
 Sat, 30 Mar 2013 19:50:03 +0000 (UTC)
 (envelope-from gnats@FreeBSD.org)
Received: from freefall.freebsd.org (freefall.freebsd.org
 [IPv6:2001:1900:2254:206c::16:87])
 by mx1.freebsd.org (Postfix) with ESMTP id B17BF907
 for <freebsd-ports-bugs@smarthost.ysv.freebsd.org>;
 Sat, 30 Mar 2013 19:50:03 +0000 (UTC)
Received: from freefall.freebsd.org (localhost [127.0.0.1])
 by freefall.freebsd.org (8.14.6/8.14.6) with ESMTP id r2UJo2EF004841
 for <freebsd-ports-bugs@freefall.freebsd.org>; Sat, 30 Mar 2013 19:50:02 GMT
 (envelope-from gnats@freefall.freebsd.org)
Received: (from gnats@localhost)
 by freefall.freebsd.org (8.14.6/8.14.6/Submit) id r2UJo2eF004840;
 Sat, 30 Mar 2013 19:50:02 GMT (envelope-from gnats)
Date: Sat, 30 Mar 2013 19:50:02 GMT
Message-Id: <201303301950.r2UJo2eF004840@freefall.freebsd.org>
To: freebsd-ports-bugs@FreeBSD.org
Cc: 
From: Darren Pilgrim <ports.maintainer@evilphi.com>
Subject: Re: ports/177416: mail/postgrey has surfaced a bug in perl's taint
 checking
X-BeenThere: freebsd-ports-bugs@freebsd.org
X-Mailman-Version: 2.1.14
Precedence: list
Reply-To: Darren Pilgrim <ports.maintainer@evilphi.com>
List-Id: Ports bug reports <freebsd-ports-bugs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-ports-bugs>, 
 <mailto:freebsd-ports-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports-bugs>
List-Post: <mailto:freebsd-ports-bugs@freebsd.org>
List-Help: <mailto:freebsd-ports-bugs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports-bugs>, 
 <mailto:freebsd-ports-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 30 Mar 2013 19:50:03 -0000

The following reply was made to PR ports/177416; it has been noted by GNATS.

From: Darren Pilgrim <ports.maintainer@evilphi.com>
To: Paul Beard <paulbeard@gmail.com>
Cc: "bug-followup@FreeBSD.org" <bug-followup@FreeBSD.org>
Subject: Re: ports/177416: mail/postgrey has surfaced a bug in perl's taint
 checking
Date: Sat, 30 Mar 2013 12:45:15 -0700

 On 2013-03-29 19:25, Paul Beard wrote:
 > Is there a way to query for
 > what port requires a module? I keep searching but it seems like
 > everything is geared to find what ports you need to install rather
 > than what ports rely on X.
 
 `pkg_info -R <port>` or `pkg info -r <port>`
 
 > The smarter option would have been to
 > check dates in /var/db/pkg and see what was updated when this
 > started.
 
 I meant that instead of reinstalling all 600+ p5 modules themselves, 
 just reinstall the ports that use perl/p5 modules and let the dependency 
 system install them for you.  Work flow like this:
 
 1. Get list of installed perl modules;
 2. Reinstall a perl-depending port;
 3. Test postgrey;
 
 If postgrey still works, repeat from step 1.  If postgrey is now broken:
 
 4. Get a new list of installed perl modules;
 5. Compare lists from steps 1 and 4;
 6. Remove ONE of the newly-added modules;
 7. Test postgrey;
 
 If postgrey is still broken, repeat from step 6.  If postgrey now works, 
 you found the culprit module.
 
 If you get all the way through your list of perl-depending ports (not 
 the modules, the top-level ports), then you can conclude you had cruft 
 from a disused perl module.