On Mon, 2007-08-06 at 16:44 -0500, Federico Mena Quintero wrote: > Hi, > > I just saw this http://live.gnome.org/GnomeGoals/AppIcon about making > apps update the GTK+ icon cache during "make install". > > This would be fine in a tarball-only world, but I wonder if distros will > just end up patching out that part of Makefiles, and calling > gtk-update-icon-cache on their own.
Hi Federico, The Makefile.am snippet only runs gtk-update-icon-cache if DESTDIR is empty. The idea is that distros make install to a temporary DESTDIR and the actual install happens later. In this case, gtk-update-icon-cache is not called in make install and it's up to the packager to call it at the right time. This trick is common practice, used at least in fontconfig and pango too. > For example, in openSUSE we update the icon cache separately from > package installation, with the idea that the cache will only be updated > once even if many packages are installed. (The really right way may be > to use an RPM %posttrans - no idea if that works.) > > So, do we really need this in tarballs? I'd say yes. > Federico Cheers, -- behdad http://behdad.org/ "Those who would give up Essential Liberty to purchase a little Temporary Safety, deserve neither Liberty nor Safety." -- Benjamin Franklin, 1759 _______________________________________________ desktop-devel-list mailing list [email protected] http://mail.gnome.org/mailman/listinfo/desktop-devel-list
