I performed an rm -r on /var/lib/pkg
jamesh at lanl.gov
Fri Oct 19 07:12:02 PDT 2007
On Thu, 2007-10-18 at 20:11 +0100, RW wrote:
> On Thu, 18 Oct 2007 12:51:33 -0600
> James <jamesh at lanl.gov> wrote:
> > > It depends what state the ports were in at the time of the
> > > accident. If you haven't run a leaf-cutting program recently you
> > > may have old dependencies and tools that have become leaves - they
> > > may take years to show-up.
> > >
> > > _______________________________________________
> > > freebsd-questions at freebsd.org mailing list
> > > http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> > > To unsubscribe, send any mail to
> > > "freebsd-questions-unsubscribe at freebsd.org"
> > I just discovered pkg_which.
> > I'm thinking I can use this to solve my (still haven't worked on)
> > problem. Any ideas why this might be a bad idea? I essentially feed
> > it a list from /usr/ports/distfiles and move on.
> Do you have the database file? The default location is in the directory
> you deleted.
> freebsd-questions at freebsd.org mailing list
> To unsubscribe, send any mail to "freebsd-questions-unsubscribe at freebsd.org"
Feeding pkgdb/pkg_which a port creates a directory for that port
It then returned a question mark, which kind of sucked, silence being
golden in unix, but I had an entry for openmpi appear in /var/db/pkg
Is this really just meaningless grasping at straws? It looked like this
in conjunction with pkgdb -L would work.
More information about the freebsd-questions