114 lines
3.2 KiB
HTML
114 lines
3.2 KiB
HTML
<html>
|
|
<head>
|
|
<title>PackageKit</title>
|
|
<link rel="stylesheet" href="style.css" type="text/css" media="screen"/>
|
|
</head>
|
|
<body>
|
|
|
|
<table align="center" class="title">
|
|
<tr>
|
|
<td><img src="img/packagekit.png"/></td>
|
|
<td width="90%" valign="middle"><p class="title">PackageKit</p></td>
|
|
<td><img src="img/packagekit.png"/></td>
|
|
</tr>
|
|
</table>
|
|
|
|
<p>Back to the <a href="index.html">main page</a></p>
|
|
|
|
<h1>What is PackageKit?</h1>
|
|
<p>
|
|
PackageKit is a system designed to make installing and updating software
|
|
on your computer easier.
|
|
The primary design goal is to unify all the software graphical tools
|
|
used in different distributions, and use some of the latest technology
|
|
like PolicyKit to make the process suck less.
|
|
</p>
|
|
|
|
<p>
|
|
The actual nuts-and-bolts distro tool (yum, apt, conary etc-) is used in
|
|
PackageKit using compiled and scripted helpers.
|
|
PackageKit isn't meant to replace these tools, instead providing a
|
|
common set abstraction that can be used by standard GUI and text mode
|
|
package managers.
|
|
</p>
|
|
|
|
<p>
|
|
PackageKit itself is a system activated daemon called
|
|
<code>packagekitd</code>.
|
|
Being system activated means that it's only being run when the user is
|
|
using a text mode or graphical tool, and quits when it's no longer being
|
|
used.
|
|
This means we don't delay the boot sequence or session startup and don't
|
|
consume memory when not being used.
|
|
</p>
|
|
|
|
<p>
|
|
<code>gnome-packagekit</code> is the name of the collection of graphical
|
|
tools for PackageKit to be used in the GNOME desktop.
|
|
There are also QT applications being designed, although these are not
|
|
fully functional yet.
|
|
</p>
|
|
|
|
<table>
|
|
<tr>
|
|
<td><img src="img/dialog-information.png" alt="[NOTE]"></td>
|
|
<td>
|
|
<p>
|
|
By default, PackageKit uses PolicyKit for user authentication.
|
|
This means as an admin you can specify with fine-grained control what
|
|
your users can and cannot do.
|
|
For instance, an admin could specify that unprivileged users can
|
|
update the system and do searching, but are not allowed to install or
|
|
remove packages.
|
|
For home users it's typical to ask the user for their own, or the
|
|
administrator "root" password.
|
|
With PolicyKit, all these options are possible.
|
|
</p>
|
|
</td>
|
|
</tr>
|
|
</table>
|
|
|
|
<p>
|
|
Use cases for PackageKit exist for the following scenarios:
|
|
</p>
|
|
|
|
<ul>
|
|
<li>Boot time security updates</li>
|
|
<li>Installing files automatically, e.g. openoffice-clipart</li>
|
|
<li>Installing new features, e.g. smart-card readers</li>
|
|
<li>Allowing unprivileged users to install software in a corporate
|
|
build</li>
|
|
<li>Opening unknown file formats</li>
|
|
<li>Removing dependencies for files</li>
|
|
</ul>
|
|
<p>
|
|
More details can be found on the wiki.
|
|
</p>
|
|
|
|
<p>
|
|
PackageKit and gnome-packagekit is GPL2+ licensed.
|
|
</p>
|
|
|
|
<p>
|
|
What PackageKit is not:
|
|
</p>
|
|
<ul>
|
|
<li>A huge daemon with lots of dependencies.</li>
|
|
<li>100% API stable. The API may change a little until we ship
|
|
1.0.0</li>
|
|
<li>Targeted to a particular architecture or platform.</li>
|
|
<li>Produced by any one vendor. There are many contributors helping to
|
|
get this done.</li>
|
|
</ul>
|
|
|
|
<p>
|
|
Formally, PackageKit is a D-Bus abstraction layer that allows the
|
|
session user to manage packages in a secure way using a cross-distro,
|
|
cross-architecture API.
|
|
</p>
|
|
|
|
<p>Back to the <a href="index.html">main page</a></p>
|
|
|
|
</body>
|
|
</html>
|