Date: Sat, 30 Mar 2013 20:20:01 GMT From: Paul Beard <paulbeard@gmail.com> To: freebsd-ports-bugs@FreeBSD.org Subject: Re: ports/177416: mail/postgrey has surfaced a bug in perl's taint checking Message-ID: <201303302020.r2UKK1gt010793@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: Paul Beard <paulbeard@gmail.com> To: Darren Pilgrim <ports.maintainer@evilphi.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 13:17:11 -0700 On Mar 30, 2013, at 12:45 PM, Darren Pilgrim = <ports.maintainer@evilphi.com> wrote: > 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. Not sure how to follow your plan with modules that aren't installed, at = least not without a lot of extra steps. I have a list that has origins = as well, so reading through it might not be too problematic. I don't = know how to work with uninstalled packages. What I never seem to be able = to find is the inversion of a dependency, for lack of a better = description: what port requires this one?=20 make pretty-print-build-requires-list is what I think I'm looking for.=20= Seems to me there should be a database, even a text file that one could = search, with this information. Rows of port names, columns with version, = maintainer, status, run dependencies, build dependencies, and if it was = really useful, one could extract all the files that live in a port's = directory =97 Makefile, distinfo, pkg-descr, pkg-plist, file in files/ =97= from that source, using some wrapper script. Maybe that already = exists=85?=20 Right now I have 21(!) p5-* ports installed and everything seems to = work. I'm sure some breakage will emerge before too long but to go from = 600 to 21 with no immediate issues tells the tale. I've removed a few = ports that were probably installed as build dependencies. I've run = through pkgdb -Fa to sort out dependencies and remove ports that I don't = need and with them, their dependencies. What would be interesting would = some way to know, short of remembering, when some binary was last used = as a way of validating the port's necessity.=20 -- Paul Beard Are you trying to win an argument or solve a problem?=20
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201303302020.r2UKK1gt010793>