> >
> > > > ok, so i wrote a small script (tcl, since i don't know perl), that
> > > > does some checking, it reports for each package, the number of files
> > > > how many are realy there, and if so, checks the MD5.
> > > >
> > > > now, if im not to far off, if some/all files are missing, or if the
> > > > md5 does not match, i should be able to remove the package info, ...
> > >
> > > Well, that's not what you were asking for originally, and tools
> > > already exist to check that.
> >
> > OK, let me refrase it
> >
> > PROBLEM:
> > how to update /var/db/pkg, when it knows too much,
> > i.e. /usr/local has less stuff that /var/db/pkg knows about.
> >
> > >
> > > e.g. pkg_info -g and the example from the pkg_which(1) manpage that I
> > > mentioned to you in a previous email.
> >
> > i read most of the pkg*, and though im very impressed, i fail to find a
> > clear/easy way to get a one line output saying:
> > pkg xyz no longer exits, can be removed from database
> > thanks,
> > danny
>
> If you know that package XYZ exists in /var/db/pkg but isn't in /usr/local
> (probably because you didn't 'make deinstall' or pkg_delete it), just do
> this:
>
> rm -rf /var/db/pkg/XYZ
>
sorry, no points. it's a correct answer but that was/is not the question :-)
how do you know that XYZ is no longer there?
sure, pkg_info -g will tell you which files are no longer there, or have bad
md5, but is one file? or all files?
danny
> --
> Matt Emmerton
>
_______________________________________________
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
