Date: Sat, 30 Mar 2013 19:50:02 GMT From: Darren Pilgrim <ports.maintainer@evilphi.com> To: freebsd-ports-bugs@FreeBSD.org Subject: Re: ports/177416: mail/postgrey has surfaced a bug in perl's taint checking Message-ID: <201303301950.r2UJo2eF004840@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201303301950.r2UJo2eF004840>