http://blogs.gnome.org/hughsie/2007/08/23/packagekit-requiring-a-restart/ Blog about geeky stuff Sun, 29 Jan 2012 09:38:55 +0000 hourly 1 http://wordpress.org/?v=3.3.1 http://blogs.gnome.org/hughsie/2007/08/23/packagekit-requiring-a-restart/comment-page-1/#comment-109 Anonymous Thu, 23 Aug 2007 11:03:08 +0000 http://blogs.gnome.org/hughsie/2007/08/23/packagekit-requiring-a-restart/#comment-109 Hi hughsient, first I'd like to thank you for the efforts you put into PackageKit. I think that this is a great project, and that it has great potential. I'd suggest to change "A system reboot is required" to something like "In order to apply the changes, a system reboot is required." or something like that. Sorry, I am no native speaker, but that sounds better to me :) Also, an interface to browse desktop applications would be nice so that the full names of applications appear instead of names like "totem-mozilla, epiphany-browser" and so on. Ubuntu has a nice tool, screenshot is located here: https://bugzilla.redhat.com/bugzilla/attachment.cgi?id=160692 maybe some code could be taken from it. As far as I know, they look which desktop files packages install and generate a package containing them (maybe modified?). Those .desktops are displayed in the application. This is - of course - not optimal for a tool which aims to work on multiple distributions. Hi hughsient, first I'd like to thank you for the efforts you put into PackageKit. I think that this is a great project, and that it has great potential. I'd suggest to change “A system reboot is required” to something like “In order to apply the changes, a system reboot is required.” or something like that. Sorry, I am no native speaker, but that sounds better to me Also, an interface to browse desktop applications would be nice so that the full names of applications appear instead of names like “totem-mozilla, epiphany-browser” and so on. Ubuntu has a nice tool, screenshot is located here: https://bugzilla.redhat.com/bugzilla/attachment.cgi?id=160692 maybe some code could be taken from it. As far as I know, they look which desktop files packages install and generate a package containing them (maybe modified?). Those .desktops are displayed in the application. This is – of course – not optimal for a tool which aims to work on multiple distributions.

]]>