(now at 100%) |
|||
(2 intermediate revisions by 2 users not shown) | |||
Line 10: | Line 10: | ||
== Current status == | == Current status == | ||
* Targeted release: Fedora12 | * Targeted release: Fedora12 | ||
* Last updated: 2009-07 | * Last updated: 2009-08-07 | ||
* Percentage of completion: 100% | * Percentage of completion: 100% | ||
PackageKit-command-not-found is optional in comps. It is included in the desktop spin. | |||
== Detailed Description == | == Detailed Description == | ||
Line 56: | Line 58: | ||
== Release Notes == | == Release Notes == | ||
* PackageKit now | * PackageKit now provides a command-not-found handler for bash so that missing commands can be installed, or invalid commands can be corrected. To use this functionality, install the PackageKit-command-not-found package. | ||
== Comments and Discussion == | == Comments and Discussion == |
Latest revision as of 14:34, 20 August 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-08-07
- Percentage of completion: 100%
PackageKit-command-not-found is optional in comps. It is included in the desktop spin.
🔗 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-found
package 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.conf
has fairly complete usage notes- There's a screencast here: http://people.freedesktop.org/~hughsient/temp/pk-command-not-found.ogv
🔗 Release Notes
- PackageKit now provides a command-not-found handler for bash so that missing commands can be installed, or invalid commands can be corrected. To use this functionality, install the PackageKit-command-not-found package.
🔗 Comments and Discussion