On Tuesday 08 of June 2010, Cristian Morales Vega wrote:
Icon Theme Specification says "any implementation that does caching is required to look at the mtime of the toplevel icon directories when doing a cache lookup, unless it already did so less than 5 seconds ago" (http://standards.freedesktop.org/icon-theme-spec/latest/ar01s08.html). ... I'm not very sure about how KDE works (neither about how to check if the icon cache has been updated). It works even without changing the mtime of the the toplevel directory? It's my understanding that at KDE start kbuildsycoca4 is run and then any new change is detected by kded. They take responsability of the icon cache, true? I suppose kded doesn't looks at the mtime of the toplevel directory since it knows exactly which icons have been added/removed/modified and so it can do a more efficient cache update. But kbuildsycocac4 checks the mtime of the toplevel directory or it recreates the cache unconditionally at every KDE start?
The class used for icon caching checks all directories, not just the toplevel one, so it is always safe. There shouldn't be any problems with KDE, regardless of how the icons are handled on openSUSE.
Between, looking at Fedora it seems they understand "toplevel directory" as the theme directory (%{_datadir}/icons/hicolor instead of %{_datadir}/icons), it's that correct?
That should be correct. -- Lubos Lunak openSUSE Boosters team, KDE developer l.lunak@suse.cz , l.lunak@kde.org -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org