OpenG Package Manager (OGPM) Overview
The OGPM consists of an API which provides services to higher-level User Interface
based tools for pacakge management, such as the Package Builder. The OGPM is
keeps a record of the packages installed on a development system. The OGPM database
keeps a copy of installed packages in its package repository, and therefore
has a record of where installed files are located, which files are documentation,
and what dependancies a package has. The OGPM has package query and verification
services that allow one to programatically access package information, and verify
that the package is installed correctly.
- Inter-package Dependency and Conflict Management
- Networked Package Repository and Directory Interface
- Package Query
- Package Verification
OGPM Design Goals
- Packages should be able to download their dependencies over the Internet.
- HTTP or FTP file download should be supported.
- OpenG should maintain a package repository.
- Packages should be distributed as a single file. This will allow easy distribution.
- A CD of all known packages should be made available for purchase (nominal
fee) and download (ISO image).
- Package manager should automate the uninstall of existing packages when
installing new versions
Development System Verification
- Individual Packages should be able to be verified, such that one can be
sure that the files are the same as when the package was installed.
Development System Configuration Management
A developer should be able to export and import development system configuration
settings. These will contain information on what packages are installed and what
the dependency tree looks like. A configuration file should be able to be imported
on another system and the required packages should be downloaded and installed.
Developers should be able to see which packages are installed and what the
package dependency tree looks like.