Software system simplifies installation and updating processes for your computer applications.
The PackageKit project is designed to simplify the installation and update of software on your computer. The project's main aim is to bring all graphical tools used in various distributions together and use new technologies like PolicyKit to make the process easier. The project uses the actual distro tool like yum, apt, conary, etc using compiled and scripted helpers. The project doesn't replace these tools but provides a common set of abstractions that standard GUI and text mode package managers can use.
PackageKit uses a system activated daemon called packagekitd that's only run when the user is using a graphical tool or text mode, meaning it doesn't delay boot or session start-up and doesn't consume memory when not in use. For GNOME desktop, graphical tools are available named gnome-packagekit, but there are still QT applications being designed that are not yet fully functional.
By default, PackageKit uses PolicyKit for user authentication, which allows admins to fine-tune user permissions. For instance, an admin can allow non-privileged users to update and search the system but disallow installation or removal of packages. Home users may input their own or the admin's "root" password. All these options are possible with PolicyKit.
PackageKit has several use cases, including boot-time security updates, automatic file installations like openoffice-clipart, installing new features like smart-card readers, allowing non-privileged users to install software in a corporate build, opening unknown file formats, and removing dependencies for files. More information can be found on the project's wiki.
PackageKit and gnome-packagekit are both GPLv2+ licensed, meaning they can be redistributed and/or modified under the terms of the GNU General Public License published by the Free Software Foundation, either version 2 of the license or any later version.
PackageKit is not a large daemon with numerous dependencies or 100% API stable. The API may change slightly before the eventual release of 1.0.0. PackageKit isn't targeted to a specific architecture or platform, nor is it produced by a single vendor. Several contributors are working collectively to complete the project. Formality sees PackageKit as a D-Bus abstraction layer that allows session users to manage packages in a cross-distribution, cross-architecture API securely.
PackageKit uses a system activated daemon called packagekitd that's only run when the user is using a graphical tool or text mode, meaning it doesn't delay boot or session start-up and doesn't consume memory when not in use. For GNOME desktop, graphical tools are available named gnome-packagekit, but there are still QT applications being designed that are not yet fully functional.
By default, PackageKit uses PolicyKit for user authentication, which allows admins to fine-tune user permissions. For instance, an admin can allow non-privileged users to update and search the system but disallow installation or removal of packages. Home users may input their own or the admin's "root" password. All these options are possible with PolicyKit.
PackageKit has several use cases, including boot-time security updates, automatic file installations like openoffice-clipart, installing new features like smart-card readers, allowing non-privileged users to install software in a corporate build, opening unknown file formats, and removing dependencies for files. More information can be found on the project's wiki.
PackageKit and gnome-packagekit are both GPLv2+ licensed, meaning they can be redistributed and/or modified under the terms of the GNU General Public License published by the Free Software Foundation, either version 2 of the license or any later version.
PackageKit is not a large daemon with numerous dependencies or 100% API stable. The API may change slightly before the eventual release of 1.0.0. PackageKit isn't targeted to a specific architecture or platform, nor is it produced by a single vendor. Several contributors are working collectively to complete the project. Formality sees PackageKit as a D-Bus abstraction layer that allows session users to manage packages in a cross-distribution, cross-architecture API securely.
What's New
Version 0.5.2: N/A