On Tue, 16 Jun 2020 16:59:07 -0400, "Jeremy O'Brien" <[email protected]> wrote:
> I wrote a quick little tool here: > https://github.com/neutralinsomniac/obsdpkgup in Go to show available > package upgrades from your configured mirror. > > It takes no more than a few seconds (the time it takes to download > index.txt from the package repo) to show you all packages that have > received a version bump. This tool *won't* show same-version > package-rebuild upgrades, so it shouldn't be used as a complete > replacement to running 'pkg_add -u', but rather as a companion to > show when actual newer versions of packages are released. I just > noticed that in my 99% case, I was waiting anywhere from 5-10 minutes > for 'pkg_add -u' to complete checking all ~400 of my installed > packages, and it uses a considerable amount of bandwidth while doing > so. > > As I understand it, the pkgtools detect same-version rebuilds by > downloading enough of every installed package tgz to check the > metadata contained within to determine if an upgrade is needed. If > anyone knows of an alternative way to determine when a same-version > package install is required, I would love to know of it. In the > meantime, I hope someone else can make use of this tool as well. I think if I wanted to compare packages between a machine of mine and a mirror, I would compare the quirks package signature timestamps. On your machine you can find it with $ grep digital-signature /var/db/pkg/quirks*/+CONTENTS and on the mirror, you need to fetch the quirks-XXX.tgz (I guess you can find the XXX with the index.txt) and then look for the +CONTENTS file. Cheers, Daniel
