Le lundi 09 août 2010, à 23:18 +0200, Lubos Lunak a écrit :
On Monday 09 of August 2010, Vincent Untz wrote:
Le lundi 09 août 2010, à 14:41 +0200, Lubos Lunak a écrit :
You could update the cache on-demand, as KDE does, instead of running it from SuSEconfig (which is actually sometimes pretty annoying on a KDE system with few rarely-used Gtk apps).
I'm sorry, can you elaborate:
+ when you say "on-demand", do I understand right that you are talking about a user cache, and not a system-wide cache? (FWIW, upstream prefers a system-wide cache for this)
User cache. If you'd want a system cache, I don't see any other way than a setuid wrapper that run the tool as root.
The setuid wrapper is not really an option, I guess. Nobody likes that :-)
BTW I don't quite see the point of having a huge system cache, do you happen to know how that is supposed to make anything better?
Why would it be huge? It's really just a cache for some system data, so there's no reason to not make it system-wide. I don't claim it's "better". It's just a way to share more things between users, since there's no reason to not share this.
+ why it SuSEconfig annoying on a KDE system with few rarely-used GTK+ apps? It it SuSEconfig itself? Is it gtk-update-icon-cache? Is it because people have to manually run it? Is it because it takes time after installing packages?
Because creating the icon cache can take long, after installing packages.
It doesn't take that long if it's done only once, does it? Does it really make a big difference compared to, say, downloading 5MB for a package?
And note that on-demand would save the trouble with people having to run anything manually.
Agree, we don't want to force people to run something manually. Vincent -- Les gens heureux ne sont pas pressés. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org