| 1 |
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> |
| 2 |
<html xmlns="http://www.w3.org/1999/xhtml"> |
| 3 |
<head> |
| 4 |
<title>PackageKit - Where can I download it?</title> |
| 5 |
<meta http-equiv="Content-Type" content="text/html; charset=utf-8"/> |
| 6 |
<link rel="stylesheet" href="style.css" type="text/css" media="screen"/> |
| 7 |
</head> |
| 8 |
<body> |
| 9 |
|
| 10 |
<table align="center" class="title"> |
| 11 |
<tr> |
| 12 |
<td><img src="img/packagekit.png" alt=""/></td> |
| 13 |
<td width="95%" valign="middle"><p class="title">Where can I download it?</p></td> |
| 14 |
<td><img src="img/packagekit.png" alt=""/></td> |
| 15 |
</tr> |
| 16 |
</table> |
| 17 |
|
| 18 |
<p>Back to the <a href="index.html">main page</a></p> |
| 19 |
|
| 20 |
<h1>Where do I download it?</h1> |
| 21 |
|
| 22 |
<h2>Precompiled Packages</h2> |
| 23 |
<p> |
| 24 |
Your distribution probably has compiled packages that are much |
| 25 |
easier to install. |
| 26 |
</p> |
| 27 |
|
| 28 |
<h2>Released Versions</h2> |
| 29 |
<p> |
| 30 |
Released versions are found on |
| 31 |
<a href="http://www.freedesktop.org/software/PackageKit/releases/"> |
| 32 |
http://www.freedesktop.org/software/PackageKit/releases/</a>. |
| 33 |
</p> |
| 34 |
|
| 35 |
<h2>Compiling the latest code</h2> |
| 36 |
<p> |
| 37 |
You can get the latest PackageKit daemon from the |
| 38 |
<a href="https://github.com/PackageKit/PackageKit">public git repositories</a>. |
| 39 |
</p> |
| 40 |
<pre> |
| 41 |
git clone https://github.com/PackageKit/PackageKit.git |
| 42 |
</pre> |
| 43 |
<p> |
| 44 |
If you want to commit changes or add a new backend, then please email the |
| 45 |
mailing list and we can give you access to a developer server. |
| 46 |
</p> |
| 47 |
|
| 48 |
<h2>Adding backends to PackageKit</h2> |
| 49 |
<p> |
| 50 |
PackageKit itself is an abstract daemon, the only bits that are distro |
| 51 |
specific are the backends. |
| 52 |
</p> |
| 53 |
<p> |
| 54 |
To make PackageKit work on a new distribution, you have to write a |
| 55 |
"backend" which is basically a shim layer from the distro tool to |
| 56 |
packagekitd. A backend can have one or more threads and also spawn other processes. |
| 57 |
</p> |
| 58 |
<p> |
| 59 |
See the developer information <a href="gtk-doc/index.html">here</a> for more |
| 60 |
information. |
| 61 |
</p> |
| 62 |
|
| 63 |
<p> |
| 64 |
Backends do not have to be complete; often they just contain basic |
| 65 |
functionality to install and remove but do not provide dependency or file |
| 66 |
lists for example. See the FAQ <a href="pk-faq.html">here</a> for backends status. |
| 67 |
</p> |
| 68 |
|
| 69 |
<p>Back to the <a href="index.html">main page</a></p> |
| 70 |
|
| 71 |
<p class="footer"> |
| 72 |
Copyright <a href="mailto:[email protected]">Richard Hughes 2007-2013</a><br/> |
| 73 |
<a href="http://validator.w3.org/check/referer">Optimized</a> |
| 74 |
for <a href="http://www.w3.org/">standards</a>. |
| 75 |
</p> |
| 76 |
|
| 77 |
</body> |
| 78 |
</html> |