Debian Codegraph @

docs/api/spec/pk-introduction.xml

raw
1 <?xml version="1.0" encoding="ISO-8859-1"?>
2 <!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN" "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd">
3
4 <chapter id="introduction">
5 <title>PackageKit Introduction</title>
6
7 <sect1 id="introduction-description">
8 <title>Overall Description</title>
9
10 <para>
11 PackageKit is a small open source system that abstracts out common package
12 management tasks such as:
13 </para>
14 <itemizedlist>
15 <listitem>
16 <para>
17 Checking for updates and installing them in the background.
18 </para>
19 </listitem>
20 <listitem>
21 <para>
22 Automatically installing new or add-on software.
23 </para>
24 </listitem>
25 </itemizedlist>
26
27 <para>
28 PackageKit has a modular design with an asynchronous API for client programs,
29 a flexible queuing module, and run-time selectable backends.
30 </para>
31
32 <mediaobject id="pk-structure">
33 <imageobject>
34 <imagedata format="PNG" fileref="pk-structure.png" align="center"/>
35 </imageobject>
36 </mediaobject>
37 </sect1>
38
39 <sect1 id="introduction-backends">
40 <title>Backends</title>
41 <para>
42 A backend is just a compiled <literal>.so</literal> object that is
43 loaded at run-time and provides an interface to the underlying package
44 commands.
45 A backend converts an asynchronous request into either a new thread
46 in the same process, or executes external "glue" files that
47 can be written in any language.
48 </para>
49 <para>
50 Backends do not have to support all of the commands supported
51 by PackageKit. Each backend advertises the commands and
52 options it supports, and the frontend will only show UI
53 elements for those commands.
54 </para>
55 </sect1>
56
57 </chapter>
58