On Sun, Oct 16, 2011 at 06:00:44PM +0000, JB wrote: > Hi, > > this is what PackageKit does to shell: > > $ dmesh --help > Usage: > pk-command-not-found [OPTION...] > > PackageKit Command Not Found > > Help Options: > -h, --help Show help options > $ > > # yum remove PackageKit-command-not-found > ... > Removed: > PackageKit-command-not-found.i686 0:0.6.12-4.fc14 > > Complete! > # > > $ dmesh --help > bash: /usr/libexec/pk-command-not-found: No such file or directory > $ > Note: exiting and restarting terminal will fix this one. > > This is not a bug, this is a misfeature of PackageKit, it should not be in > it in the first place. > It has been discussed on the list at time of F13 and rejected by users. > I have reported it to PackageKit devs a year ago. > https://bugzilla.redhat.com/show_bug.cgi?id=641311 > > There is a good UNIX tradition and principle - one utility, one function. > Let PackageKit do package management. > Let shell utility do command language interpretation (command line, etc). I always remove and disable as much of PackageKit as possible too, including this pk-command-not-found misfeature. However I don't agree with you -- you can remove 'PackageKit-command-not-found' and after restarting the shell you won't be bothered by it again. You can disable the PK daemon too. Now if in future it became impossible to remove PackageKit-command-not-found, then that would be very bad. However I don't think anyone, including Richard Hughes, would want that. Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones New in Fedora 11: Fedora Windows cross-compiler. Compile Windows programs, test, and build Windows installers. Over 70 libraries supprt'd http://fedoraproject.org/wiki/MinGW http://www.annexia.org/fedora_mingw -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel
