| Where can I download it? |

Back to the main page

# Where do I download it?

## Precompiled Packages

Your distribution may already have compiled packages that are much easier to install.

- Conary: Yes, just run: `sudo conary update PackageKit gnome-packagekit`
- Fedora 9: Yes, just run: `yum install PackageKit gnome-packagekit` (as root)
- Ubuntu: Ubuntu 8.04 Hardy Heron ships an obsolete version (0.1.6) of PackageKit by default. Intrepid, the upcoming Ubuntu release, features a recent version from the 0.3 series.
  You can find the latest version of the 0.3 series for Hardy and Intrepid in this Personal Package Archive. Add the repository and install the packages `packagekit` and `packagekit-gnome`.
- openSUSE 11: Yes, add this repository file and run: `zypper install PackageKit gnome-packagekit` (as root)
- Mandriva 2009 : Yes, just run: `urpmi packagekit gnome-packagekit` (as root)
- Others: Probably not, although you can compile from source. See below for more details.

## Released Versions

Released versions are found on http://www.packagekit.org/releases/.

### Latest Supported Versions:

These are versions which have new features for each release. We are also willing to break ABI and API to fix bugs and will merge new or modified translations as required or suggested. Releases are normally once every 3-4 weeks.

Version |  | Date
0.5.0 |  | 2009-07-06
0.5.1 |  | 2009-08-03

### ABI Stable Versions:

These are versions where we will not break ABI, API or localisations. Releases are less frequent, usually every few months.

Version |  | Date
0.4.8 |  | 2009-06-01
0.4.7 |  | 2009-05-05
0.4.6 |  | 2009-03-30
0.4.5 |  | 2009-03-09
0.4.4 |  | 2009-02-23
0.4.3 |  | 2009-02-02
0.4.2 |  | 2009-01-19
0.4.1 |  | 2009-01-08
0.4.0 |  | 2008-12-09

### Obsolete Versions:

These are versions that used to be the ABI stable releases, but are now longer supported. There will not be any more releases of these versions.

Version |  | Date
0.3.16 |  | 2009-06-10
0.3.15 |  | 2009-03-30
0.3.14 |  | 2009-02-02
0.3.12 |  | 2008-12-08
0.3.11 |  | 2008-11-24
0.3.10 |  | 2008-11-10
0.3.9 |  | 2008-10-27
0.3.8 |  | 2008-10-20
0.3.7 |  | 2008-10-13
0.3.6 |  | 2008-10-06
0.3.5 |  | 2008-09-29
0.3.4 |  | 2008-09-22
0.3.3 |  | 2008-09-16
0.3.2 |  | 2008-09-08
0.3.1 |  | 2008-08-27
0.3.0 |  | 2008-08-18
0.2.5 |  | 2008-09-06
0.2.4 |  | 2008-07-30
0.2.3 |  | 2008-07-04
0.2.2 |  | 2008-06-05
0.2.1 |  | 2008-05-09
0.2.0 |  | 2008-05-06
0.1.11 |  | 2008-04-05
0.1.10 |  | 2008-03-28
0.1.9 |  | 2008-03-04
0.1.8 |  | 2008-02-21
0.1.7 |  | 2008-02-14
0.1.6 |  | 2008-01-18
0.1.5 |  | 2007-12-21
0.1.4 |  | 2007-11-26
0.1.3 |  | 2007-11-10
0.1.2 |  | 2007-11-01
0.1.1 |  | 2007-10-23
0.1.0 |  | 2007-10-16

## Dependencies

The actual PackageKit daemon requires:

- `glib` 2.14.0
- `dbus` newer than 1.1.3 (20070819 or later)
- `dbus-glib` 0.74
- `libnm` 0.6.4 (optional)
- `polkit-dbus` 0.5
- `polkit-grant` 0.5

gnome-packagekit will need all the usual GNOME libs as well. Just make sure you install PackageKit before gnome-packagekit!

## Compiling the latest code

You can get the latest PackageKit daemon and GNOME frontend from the public git repositories on freedesktop:

    git clone git://anongit.freedesktop.org/git/packagekit/PackageKit
    git clone git://git.gnome.org/gnome-packagekit

KPackageKit is available from svn in the KDE playground:

    svn co svn://anonsvn.kde.org/home/kde/trunk/playground/sysadmin/kpackagekit

There are detailed build instructions for different distros available:

- Fedora

If you want to commit changes or a new backend, then please email the mailing list and we can give you access to a developer server. The developer server is always up to date, and the anonymous git is synced about twice a day. Having a two tier server lets developers review code for correctness and security problems before it's used in the real world.

## Adding backends to PackageKit

PackageKit itself is an abstract daemon, the only bits that are distro specific are the backends.
To make PackageKit work on a new distribution, you have to write a "backend" which is basically a shim layer from the distro tool to packagekitd. A backend can have one or more threads and also spawn other processes.
See the developer information here for loads more information.

Backends do not have to be complete; often they just contain basic functionality to install and remove but do not provide dependency or file lists for example. See the FAQ here for backends status.

We need people to create backends, and then package (pardon the pun) PackageKit and gnome-packagekit for more distributions. I think it's important that installing and updating software should be as easy as possible.

Back to the main page