From 106d0fc541ad21306f5722e0178171eef6a222e9 Mon Sep 17 00:00:00 2001 From: Dave Reisner Date: Sat, 9 Mar 2013 18:28:28 -0500 Subject: 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 Signed-off-by: Allan McRae --- lib/libalpm/be_local.c | 1 + 1 file changed, 1 insertion(+) (limited to 'lib/libalpm/be_local.c') diff --git a/lib/libalpm/be_local.c b/lib/libalpm/be_local.c index 49b1c742..2c18a453 100644 --- a/lib/libalpm/be_local.c +++ b/lib/libalpm/be_local.c @@ -1091,6 +1091,7 @@ alpm_db_t *_alpm_db_register_local(alpm_handle_t *handle) } db->ops = &local_db_ops; db->handle = handle; + db->usage = ALPM_DB_USAGE_ALL; if(local_db_validate(db)) { /* pm_errno set in local_db_validate() */ -- cgit v1.2.3-24-g4f1b