BackgroundPackageInstallation

Differences between revisions 3 and 4
⇤ ← Revision 3 as of 2006-07-22 00:29:26 →
Size: 1514
Editor: d66-183-174-128
Comment: add use case, move design, add rationale and implmentation and smart
← Revision 4 as of 2006-07-22 00:32:17 → ⇥
Size: 1578
Editor: d66-183-174-128
Comment: add link to spec
Deletions are marked like this. Additions are marked like this.
Line 4: Line 4:
 * '''Launchpad entry''': none yet  * '''Launchpad entry''': https://launchpad.net/distros/ubuntu/+spec/background-package-processing

Summary

Separate the frontend and backend for package administration completely and communicate using dbus.

Rationale

Installing a package should not block the UI of the application being used, be it gnome-app-install or synaptic.

Use cases

  • Jim wants to install a package, but also wants to keep browsing through the catalogue. As he has dialup, he knows it is going to take a while for it to download.

Scope

Design

The frontends for package administration, e.g. gnome-app-install, synaptic or update-manager, only do the selection part and send the data of packages to be removed or installed via dbus to a system installation service. This allows to use different package management system for the same frontends.

http://tw.apinc.org/weblog/2006/05/26#summer-of-code-acceptance https://launchpad.net/distros/ubuntu/+source/synaptic/+bug/17138

Implementation

  • Add dbus communication to smart
  • Add ability to communicate over dbus to gnome-app-install, etc.

Code

Data preservation and migration

Unresolved issues

BoF agenda and discussion

CategorySpec

BackgroundPackageInstallation (last edited 2008-08-06 16:24:37 by localhost)