On Sat, 2008-06-14 at 16:55 +0100, Peter Tribble wrote: > On Fri, Jun 6, 2008 at 8:55 PM, Erwann Chenede <Erwann.Chenede at sun.com> > wrote: > > > > The general design for each service script is to check if the cache is > > older than the items it is meant to cache if so the cache is regenerated. > > This ensure the time spent at boot time by these services is minimum if no > > package upgrade happened. > > Is this logic valid? I can think of at least 2 cases when it fails: > > - if something is removed, then the find won't find it at all
You're right, this is a problem with some of these services. For example icon-cache should be rebuilt if icons are removed. Unfortunately we cannot uninstall the gconf schemas when they are removed because we would need the .schemas files for that (i.e. we could only do it as a preremove action), but fortunately having extra config settings is not toxic. We need to review this. > - if whatever's putting files in changes the timestamps, then the find > will be confused There are plenty of ways to do harm, but I don't think we can be prepared for everything. > It would be safer to always regenerate. What you need is to know whether > packaging installed or removed anything; you can't rely on find to answer > that. Always regenerating would take about an extra 30 sec at each boot on a reasonable machine. > Presumably these all need to run in zones as well? Well, they should but some of them can't. The bugs are in the GNOME code, though, not in these services. Laca
