Re: [Scrollkeeper-devel] Scrollkeeper delay

[Malcolm T. <ma...@co...>]

On Fri, 2003-06-20 at 21:09, Pablo Fernandez wrote:
> I'm a Gnome enthusiastic, I developed Cronos II which is an mail client
> for Gnome.
> 
> I work now at a company that is developing a Linux distribution based on
> KDE and the problem which is the reason I contact you people is that
> none of my coworkers like Gnome and nothing related to it, but I
> insisted too much and they agreed to install Gnome as well. 

Sounds like you have bigger problems, too, since scrollkeeper is
designed to support more than GNOME. Unpleasant. :(

> The problem is that the installation is about 15 minutes longer due to
> scrollkeeper, since it rebuilds it database like five times.

Well, it adds something to the database once for every package with an
OMF file. This problem is _only_ going to bite you on a brand new
install, though, since that is when you are installing a bunch of
packages that use scrollkeeper. There is not really any other way to do
it, either, since there is no way for a package to know if it is being
installed as part of a set or not. Note that exactly the same problem
applies with respect to running, for example, ldconfig when installing
shared libraries. Of course, you don't notice the difference there,
since everything uses shared libraries.

One has to wonder how often your colleagues think people are going to be
installing their machines from scratch. And if the difference is only
fifteen minutes and ... *sigh*. Might as well give up now. :-(

> I been reading the code and I didn't found a way to avoid this, thus why
> I'm writting this. 
> 
> Is there anyway to avoid the rebuild of the database without rebuilding
> the packages that use the scrollkeeper-update program?

Not easily. An ugly, but possibly workable solution would be to
temporarily alias the scrollkeeper-update name to something harmless
like ':' and then run scrollkeeper-update once as part of some
post-install fixup.

Malcolm