PackageKit
 |
This article relies on references to primary sources or sources affiliated with the subject, rather than references from independent authors and third-party publications. Please add citations from reliable sources. (September 2011) |
 |
|
 gnome-packagekit, a front-end for PackageKit, running on Fedora |
|
| Developer(s) | Richard Hughes |
|---|---|
| Stable release | [±] |
| Development status | Active |
| Written in | C, C++, Python |
| Operating system | Linux |
| Type | Package management system |
| License | GNU General Public License |
| Website | www.packagekit.org |
PackageKit is an open source and free suite of software applications designed to provide a consistent and high-level front end for a number of different package management systems. PackageKit was created by Richard Hughes.
The suite is ostensibly cross-platform, though it is primarily targeted at Linux distributions which follow the interoperability standards set out by the freedesktop.org group. It uses the software libraries provided by the D-Bus and PolicyKit projects to handle inter-process communication and computer privilege negotiation.
Contents |
[edit] History
PackageKit was created by Richard Hughes and first proposed in a series of blog posts in 2007[1][2], and is now developed by a small team of developers. Fedora 9 was the first operating system to use it as default front end for yum. It has undergone many updates in Fedora 10 and Fedora 11.
[edit] Design
PackageKit itself is a system activated daemon called packagekitd, that abstracts out differences between the different systems. A library called libpackagekit also allows other programs to interact with PackageKit.[4]
Features include:
- Installing local files, ServicePack media and from remote sources.
- Authorization using PolicyKit.
- Does not replace existing packaging tools.
- Multi-user system aware – will not allow shutdown in critical parts of the transaction.
- A system activated daemon so exits when not in use.
[edit] Front-ends
There are three front-ends for PackageKit:
- gnome-packagekit to be used in the GNOME desktop.
- Apper to be used in the KDE desktop.
- pkcon to be used on the command line.
[edit] Back-ends
A number of different package management systems (known as back-ends) support different abstract methods and signals that are used by the front-end tools.[5] Back-ends supported include:
- Advanced Packaging Tool (APT),
- Arch Linux Package Management (ALPM),
- box,
- Conary,
- Sabayon Linux's Entropy,
- Opkg,
- PiSi,
- poldek,
- Portage,
- razor,
- Smart Package Manager,
- YUM,
- ZYpp.
- urpmi.
[edit] See also
[edit] References
- ^ "Installing and Updating Software Blows Goats". Richard Hughes. http://blogs.gnome.org/hughsie/2007/07/27/installing-and-updating-software-blows-goats/. Retrieved 18 January 2011.
- ^ "Robert Hughes' blog posts about PackageKit". Richard Hughes. http://blogs.gnome.org/hughsie/?s=PackageKit. Retrieved 18 January 2011.
- ^ "KpackageKit: future of package managers on your desktop". polishlinux.org. http://polishlinux.org/kde/kpackagekit-interview/. Retrieved 10 July 2009.
- ^ "PackageKit Reference Manual". packagekit.org. http://www.packagekit.org/gtk-doc/PkClient.html. Retrieved 10 July 2009.
- ^ "Frequently asked questions". packagekit.org. http://www.packagekit.org/pk-faq.html#how-complete. Retrieved 10 July 2009.
[edit] External links
|
||||||||||||||||
 |
This free software-related article is a stub. You can help Wikipedia by expanding it. |
