13.6. Repositories

A Repository is a collection of packages. The most frequently used repository is the system repository, which lists packages installed by LPMtool. The system repository's structure is described in Chapter 14. Other kinds of repositories include remote web sites that offer packages available for download.

A Repository provides methods for:

• Enumerating all packages in the repository, and checking if a specific package exists. The packages are enumerated as NAVR objects.

• Returning a Manifest of a specific package.

• Returning Resource Databases that represent all required, provided, conflicting, and updated dependencies from all packages in the repository. These Resource Databases contain a combined list of corresponding resources from all packages in the repository.

• Returning a Resource Database that represents all triggers. A trigger is a script whose execution is triggered by an installation or uninstallation of a resource. The script itself is stored as a part of a package's manifest, and a a Resource Database provides a way to quickly locate packages with matching triggers.

  This Resource Database holds dependencies whose resources are named "triggerin-resource", "triggerun-resource", and "triggerpostun-resource", where "resource" is the name of the triggering resource. See Section 7.8.2 for more information.

• Installing a new package manifest into the repository. This entails reading all the required, provided, conflicting, and updated resources from the package's manifest, and adding them to the repository. The package's triggers are also added to the repository's trigger resource database.

• Removing a package from the repository. This entails removing the manifest, and all dependencies associated with the package, from the repository.