| commit | 79e98316ea89486d107466858543e965bcfbb0a9 | |
| author | Dan McGee <dan@archlinux.org> | |
| Wed, 8 Jun 2011 01:42:15 +0000 (7 20:42 -0500) | ||
| committer | Dan McGee <dan@archlinux.org> | |
| Fri, 24 Jun 2011 08:46:12 +0000 (24 03:46 -0500) | ||
| tree | e22572124cffc7275a200e4964c4ea112457fa52 | treesnapshot (tar.gz zip) |
| parent | 1150d9e15aaea2ae1f259995d11442f491ef0af7 | commitdiff |
Add a 'valid' flag to the database object
Start by converting all of our flags to a 'status' bitmask (pkgcache
status, grpcache status). Add a new 'valid' flag as well. This will let
us keep track if the database itself has been marked valid in whatever
fashion.
For local databases at the moment we ensure there are no depends files;
for sync databases we ensure the PGP signature is valid if
required/requested. The loading of the pkgcache is prohibited if the
database is invalid.
Signed-off-by: Dan McGee <dan@archlinux.org>
Start by converting all of our flags to a 'status' bitmask (pkgcache
status, grpcache status). Add a new 'valid' flag as well. This will let
us keep track if the database itself has been marked valid in whatever
fashion.
For local databases at the moment we ensure there are no depends files;
for sync databases we ensure the PGP signature is valid if
required/requested. The loading of the pkgcache is prohibited if the
database is invalid.
Signed-off-by: Dan McGee <dan@archlinux.org>