Re: [Scrollkeeper-devel] What about the distributions?

[Ali A. <ALI...@au...>]

On Wed, 18 Oct 2000, laszlo kovacs wrote:

> > Unfortunately - when people './configure;make;make install' they will
> > miss out on this aspect.
> > 
> > What you might need to do is to create some sort of
> > system/cron-job/daemon in which scrollkeeper checks the local files
> > installed - if it is missing it will remove them from its internal
> > database.
> > 
> > Otherwise you will need a big huge README in each project saying "please
> > run scrollkeeper-install after 'make install' is done"
> 
> Can each project have in its Makefile a section that checks for
> Scrollkeeper and if it's installed then installs the docs for
> Scrollkeeper also (same for uninstall)? I guess the problem is the large
> number of packages and distributors, but it can be done in time if the
> system (Scrollkeeper and the Help Browser) is good so distributors see
> it is better to support it.

The problem arised when you are building RPMs (for example).

You do an 'rpm -ta file.tar.gz' - It starts building and then does a 
'make install' to detect all the installed files. Unfortunately during 
this step you also do the 'scrollkeeper-install' thingy (so the file gets 
installed with scrollkeeper even though you were just BUILDING a package 
and not INSTALLING a package). 

Icky situation, right?
 
> Laszlo
>