On Thu, 28 Dec 2006 10:27:53 -0500, Christopher Aillon wrote: > Rex Dieter wrote: > > Christopher Aillon wrote: > >> Rex Dieter wrote: > >>> imo, ldconfig example isn't a good one, but I get your point. > >>> Difference being here, messing with ldconfig can horribly break > >>> things. A stale iconcache doesn't break anything, at worst only > >>> affects app startup time (a little). > > > >> Stale icon cache has been known to break apps, though. nm-applet is one > >> of them. > > > > That's either not true, or simply a bug somewhere. Matthias' has stated > > gtk2's implementation will(should!) fallback to using brute-force search > > when icon cache is not fresh. > > I'm not denying it is a bug somewhere that I'm trying to track down. > What I'm saying is that there is the potential for breaking things due > to whatever reasons. Saying that a stale cache does not cause things to > break is a little misleading until the bugs are fixed. It is a bug somewhere and the reason why gtk-update-icon-cache is executed in post-install scriptlets. It's the only way freshly installed icons show up in the GNOME desktop menu. -- Fedora-packaging mailing list Fedora-packaging@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-packaging
