summaryrefslogtreecommitdiffstats
path: root/lib/libalpm/db.h
diff options
context:
space:
mode:
authorDave Reisner <dreisner@archlinux.org>2013-03-10 00:28:28 +0100
committerAllan McRae <allan@archlinux.org>2013-09-04 01:51:20 +0200
commit106d0fc541ad21306f5722e0178171eef6a222e9 (patch)
tree6529a3b3573179ad9355e008181e724fe98ce853 /lib/libalpm/db.h
parent5f80d7afbd45100f5b5d28e43a9d9a80dde4b559 (diff)
downloadpacman-106d0fc541ad21306f5722e0178171eef6a222e9.tar.gz
pacman-106d0fc541ad21306f5722e0178171eef6a222e9.tar.xz
libalpm: introduce a usage level for repos
This defines a level of interest a user has in a repository. These are described by the bitmask flags in the alpm_db_usage_t enum: ALPM_DB_USAGE_SEARCH: repo is valid for searching ALPM_DB_USAGE_INSTALL: repo is valid for installs (e.g. -S pkg) ALPM_DB_USAGE_UPGRADE: repo is valid for sysupgrades ALPM_DB_USAGE_ALL: all of the above are valid Explicitly listing the contents of a repo will always be valid, and the repo will always be refreshed appropriately on sync operations. Signed-off-by: Dave Reisner <dreisner@archlinux.org> Signed-off-by: Allan McRae <allan@archlinux.org>
Diffstat (limited to 'lib/libalpm/db.h')
-rw-r--r--lib/libalpm/db.h1
1 files changed, 1 insertions, 0 deletions
diff --git a/lib/libalpm/db.h b/lib/libalpm/db.h
index 80292933..4bb6ee91 100644
--- a/lib/libalpm/db.h
+++ b/lib/libalpm/db.h
@@ -73,6 +73,7 @@ struct __alpm_db_t {
/* flags determining validity, local, loaded caches, etc. */
enum _alpm_dbstatus_t status;
alpm_siglevel_t siglevel;
+ alpm_db_usage_t usage;
};