On Tue, Oct 11, 2005 at 03:51:15PM +0200, Josselin Mouette wrote:
> 2. The cure
> A mmap()-able cache file format was proposed, and is generated by
> gtk-update-icon-cache in /usr/share/icons/$theme/icon-theme.cache files.
> It helps a lot to improve speed.
You mean _/var_/<something>/$theme/icon-theme.cache, don't you?
> 5. The proposed solution
> The Redhat people, who implemented the cache specification, obviously
> don't have problems with applications suddenly becoming unusable after
> some change: they started to generate cache for all directories,
> automatically adding post-installation snippets to the application
> packages. As "this worked", and as the GTK+ developers - which happen to
> be partly the same people - don't want to change the code, their
> recommendation is to do the same for Debian. Applying this solution
> means that, as soon as some packages start using the new debhelper
> snippet, hundreds of other packages will more or less break when
> installed after the cache generation.
My personal opinion that when a package modifies/extends a theme by
installing a new icon it is a reasonable requirement to somehow
"register" the changes (in this case by updating the cache file).
What about adding a script to /etc/cron.daily to regenerate the caches
on a regular basis until all applications are updated? Users of unstable
should be prepared for short breakages anyway.
Gabor
--
---------------------------------------------------------
MTA SZTAKI Computer and Automation Research Institute
Hungarian Academy of Sciences
---------------------------------------------------------
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
