This topic was discussed during the PMO call on Tuesday 5/31.
The GDP environment is somewhat different from a typical Linux distribution environment in the sense that a GDP image as such already includes all components that its build system creates. For a typical Linux distro, a basic images are created e.g. workstation, server, etc. that provide a core system. Users can then use the package management system to download and install thousands of other packages from repositories. Currently we do not have a package repository for GDP pretty much also because everything we build is already included with the GDP image. That does however not mean that we could not have it though.
In this discussion we also need to distinguish:
- Platform Package Manager (PPM): installs, updates, removes etc. packages from files and maintains the package database. The typical examples are RPM, DEB, IPK.
- Package Downloader (PD): checks a download server for new packages that apply to the system, downloads them and then defers to the platform package manager for installation (either by calling the respective executables or using libraries). Typical examples are apt-get, dnf, yum, zypper and Smart PM
The PPM for GDP currently is RPM (basically because the YP/OE default is RPM). However, it is not included with GDP. Eventually, the PD for GDP should become SOTA for which we are currently setting up the server-side infrastructure. That will grow GDP into an end-to-end platform.
Therefore my suggestion is to
- Include the PPM into the GDP (add package-management to IMAGE_FEATURES)
- Include SOTA with GDP
- Set up SOTA server-side infrastructure
If there is functionality missing in SOTA then it would make more sense to add that functionality to SOTA rather than use another system. For example, SOTA may typically push update notifications to the clients but adding functionality for a client to query the SOTA server for updates is not that hard to add.