PackageKit Command Not Found
The PackageKit command not found functionality allows command line users to automatically install missing commands, or to suggest spelling replacements.
- Name: Richard Hughes
- email: <firstname.lastname@example.org>
- Targeted release: Fedora12
- Last updated: 2009-08-07
- Percentage of completion: 100%
PackageKit-command-not-found is optional in comps. It is included in the desktop spin.
PackageKit-command-not-found package installs a handler to bash so that missing commands can be installed, or invalid commands can be corrected.
Benefit to Fedora
This feature will add the same functionality to Fedora as Ubuntu users have had for years.
This is a very small change in comps, so that the
PackageKit-command-not-found package gets included in the default package set. It's already available in Fedora 11, but not installed by default.
How To Test
yum install PackageKit-command-not-found
- Restart the terminal, or log out and log in again
- Open a terminal (gnome-terminal works well)
- Type '
gedti /boot/grub/grub.conf', and verify output is:
Command not found. Similar command is: 'gedit'
- Ensure the powertop package is removed from the system. Then type '
powertop', and verify output is:
Command not found. Install package 'powertop' to provide command 'powertop'? [N/y]
You can edit system policy by changing the
New users can get the package installed automatically when trying to use a new command. Experienced users can get spelling mistakes in commands automatically fixed.
PackageKit 0.4.x (already in F11)
PackageKit-command-not-found from comps, and revert back to doing nothing when the command is not found.
/etc/PackageKit/CommandNotFound.confhas fairly complete usage notes
- There's a screencast here: http://people.freedesktop.org/~hughsient/temp/pk-command-not-found.ogv
- PackageKit now installs a command not found handler so that missing commands can be installed, or invalid commands can be corrected.