Changes between Version 4 and Version 5 of YumDB

Show
Ignore:
Author:
james (IP: 65.172.155.230)
Timestamp:
01/06/11 20:30:46 (7 years ago)
Comment:

Expand on keys for yumdb.

Legend:

Unmodified
Added
Removed
Modified
  • YumDB

    v4 v5  
    3636 * Load all keys of XYZ from all installed packages. The only usecase here is loading the checksum data to calculate rpmdb-versions, on install/etc. ... however we need a separate index for this anyway, as we when need to know this information quickly we don't want to load the packages at all. 
    3737 
    38 == Commonly stored information == 
     38== Stored information == 
     39 
     40One of the desires for the yumdb is that users/plugins/etc. could store almost arbitrary information in the yumdb, and have it attached to specific packages. So listing a "canonical" set of keys is never going to be possible. At some point there may be an API to get a list of "keys that should migrate on a package update", but that isn't in 3.2.29 atm. 
     41 
     42So here's a list of all the items that should be set for every package (from yumdb info) from 3.2.29 onwards: 
     43 
    3944 * from_repo: the name of the repo from which the pkg was installed 
     45 * from_repo_revision: Repo. revision. Or ctime for a local package. 
     46 * from_repo_timestamp: Repo. timestamp. Or mtime for a local package. 
    4047 * reason: reason for installing this pkg (user, dep, etc) 
    41  * command_line: command line used to install this pkg 
    4248 * releasever: $releasever of the system at the time the pkg was installed (so you can look for pkgs which have lingered across release updates) 
    43  * installed_by (3.2.28): The loginuid of the user who first installed this package (can be non-existant). This doesn't cross Obsoletes. 
    44  * changed_by (3.2.28): The loginuid of the user who last installed this package (can be non-existant). 
     49 * installed_by (3.2.28): The loginuid of the user who first installed this package (note that some tools which call yum don't obey loginuid, this not being set is one of many problems that introduces). This doesn't cross Obsoletes. 
     50 * changed_by (3.2.28): The loginuid of the user who last installed this package. 
     51 
     52These are known other keys: 
     53 
     54 * checksum_type: The type of the checksum for the installed pkg. Eg. md5, sha1, sha256. 
     55 * checksum_data: The value of the checksum for the installed pkg. 
     56 * origin_url (3.2.29): Requires a newer urlgrabber, this is the url that the package was download from. 
     57 * command_line: The command line used to install this pkg (only set if pkg. installed from a tool that has a command line). 
     58 * installonly: Not set by yum, but looked at to see if installonly packages should be automatically removed. 
     59 * group_member (3.2.29+?): Set by yum if a package was installed as part of a "group install" (beta patch). 
    4560 
    4661== Accessing this information ==