Where can I download it?
Back to the main page
Your distribution may already have compiled packages that are much easier to install. Refer to the users page for more details or use the instructions provided below to get you going using your native package manager.
sudo conary update PackageKit gnome-packagekit
yum install PackageKit gnome-packagekit(as root)
apt-get install packagekit gnome-packagekit(as root).
zypper install PackageKit gnome-packagekit(as root)
urpmi packagekit gnome-packagekit(as root)
Released versions are found on http://www.packagekit.org/releases/.
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 on the first working Monday of each month.
These are versions where we will not break ABI, API or localisations. Releases are less frequent, usually every few months.
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.
The actual PackageKit daemon requires:
gnome-packagekit will need all the usual GNOME libs as well. Just make sure you install PackageKit before gnome-packagekit!
You can get the latest PackageKit daemon and GNOME frontend from the public git repositories on gitorious.org:
git clone git://gitorious.org/packagekit/packagekit.git git clone git://git.gnome.org/gnome-packagekit
Apper (was KPackageKit) is available from Git in the KDE playground:
git clone git://anongit.kde.org/apper
There are detailed build instructions for different distros available:
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.
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 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