Subject: package database consistency checks
To: None <firstname.lastname@example.org>
From: Martijn van Buul <email@example.com>
Date: 12/20/2002 16:14:30
Have I overseen things, or is there no way to check the consistency of
the dependency tree? A few weeks ago, I had a powerdip in the middle of
a massive updating session, so expected that my package database was
probably corrupt and incorrect. To my surprise, I couldn't find any
tool to check this, so I wrote something myself. Have I overlooked things,
or is this really a missing feature? It turned out that the inconsistencies
were a lot worse than I expected it to - more than this powerdip should
have caused (/var is on the rootfs, as this is my desktop system, I'm the
only user on it, and since it doesn't have any real services, and my
root filesystem isn't mounted with softupdates), so there probably already
was some "wear and tear".
So I wrote a perl-script (since I wanted to learn perl anyway, and this
seemed a good occasion, so it's probably not very correct code ;) which
compares the @blddep entries in the various +CONTENTS files against the
+REQUIRED_BY entries of the "other side".
Does this actually make sense? I'm a bit worried because I used the build
dependencies, but the @pkgdep entries were harder to parse ;) Why is such
a feature not present in pkg_admin?
Martijn van Buul - Pino@dohd.org - http://www.stack.nl/~martijnb/
Geek code: G-- - Visit OuterSpace: mud.stack.nl 3333
Kees J. Bot: The sum of CPU power and user brain power is a constant.