(accepted at 2009-07-17 FESCo meeting) |
|||
| Line 61: | Line 61: | ||
* See [[Talk:Features/PackageKitCommandNotFound]] | * See [[Talk:Features/PackageKitCommandNotFound]] | ||
[[Category: | [[Category:FeatureAcceptedF12]] | ||
<!-- When your feature page is completed and ready for review --> | <!-- When your feature page is completed and ready for review --> | ||
<!-- remove Category:FeaturePageIncomplete and change it to Category:FeatureReadyForWrangler --> | <!-- remove Category:FeaturePageIncomplete and change it to Category:FeatureReadyForWrangler --> | ||
<!-- After review, the feature wrangler will move your page to Category:FeatureReadyForFesco... if it still needs more work it will move back to Category:FeaturePageIncomplete--> | <!-- After review, the feature wrangler will move your page to Category:FeatureReadyForFesco... if it still needs more work it will move back to Category:FeaturePageIncomplete--> | ||
Revision as of 20:36, 19 July 2009
PackageKit Command Not Found
Summary
The PackageKit command not found functionality allows command line users to automatically install missing commands, or to suggest spelling replacements.
Owner
- Name: Richard Hughes
- email: <richard@hughsie.com>
Current status
- Targeted release: Fedora12
- Last updated: 2009-07-16
- Percentage of completion: 99%
Detailed Description
The 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.
Scope
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
- Install
PackageKit-command-not-foundpackage usingyum 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 /etc/PackageKit/CommandNotFound.conf file.
User Experience
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.
Dependencies
PackageKit 0.4.x (already in F11)
Contingency Plan
Drop PackageKit-command-not-found from comps, and revert back to doing nothing when the command is not found.
Documentation
- http://blogs.gnome.org/hughsie/2008/12/05/command-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
Release Notes
- PackageKit now installs a command not found handler so that missing commands can be installed, or invalid commands can be corrected.
Comments and Discussion