Overview
The Repository database is where all of the package meta-data is stored. This information is kept on the server
side, and is not necessary to be transferred to the client for proper operation. All information needed for package
installation, removal and upgrading is stored here, as well as additional information for a future web-based interface
to the distribution feeds (such as IpkgFind, administration backend, etc.).
Tables
- Distribution - distribution using a given PackageType (e.g. OpenZaurus
v3.5.4 using ipkgs)
- Device - hardware device, could be specific device (e.g. Sharp SL-C700), or broader device
grouping (e.g. Sharp SL-C7x0) - undecided
- Software - software application or library (e.g. Dagger v0.9.3)
- Package - package containing a given Software, Architecture and PackageType (e.g.
opie-dagger_0.9.3_arm.ipk)
- PackageType - packaging format (e.g. ipkg, deb, rpm, etc.)
- Depend - associates a Software with its dependent Packages
- DistComponent - associates Software with a given Distribution
- DistDevice - associates the supported Devices for a given Distribution
- DevArch - associates supported Architectures with a given Device
- Architecture - architecture a Package is compiled for (e.g. all, any, arm, armv4, etc.)
- Session - temporary table used for client information (distro, device, etc.) while client is
connected to server
- SessionPackage - temporary table containing packages installed on the device for a given
session
For detailed table definitions, here is the SQL to create the database.
Structure
