Re: [Scrollkeeper-devel] ScrollKeeper-0.1 Proposal #3

[Gregory L. <gle...@cu...>]

I'm going to snip this CC: line as I assume everybody is on the list,
and that you don't really need two copies of this stuff.


> On Tue, Nov 14, 2000 at 09:39:56AM +0000, Laszlo Kovacs wrote:
> > > Most package systems should provide a mechanism to call scrollkeeper-install
> > > after a document has been added to the system, ideally with the path in
> > > which the document was installed.  For those that don't, the system can
> > > run something periodically that re-indexes the list of installed
> > > documentation, in the same way that the apropos database is built at the
> > > moment.
> >
> > The problem with this is that packagers will have to create large
> > postinstall scripts to get it working right and some of the people on
> > this list think they will not do it if the changes are not as simple as
> > possible. If we disregard the packagers possible reaction then most/all
> > of the Scrollkeeper related process should be launched from postinstall
> > scripts. But as I said some people strongly opposed that.
> 
> How large?  
> 
> Installing the documentation and running a scrollkeeper command should be
> as trivial as installing a new library and having to run ldconfig after
> the install.


This is how the current implementation works.  The packager adds a line
that says 'scrollkeeper-update' in their post-install script, which
works in a similar manner to ldconfig.  I'd recomend download from CVS
and building Scrollkeeper.  It takes less than 5 minutes to download,
configure, build, and install here, and then I can take a look at the
source and the stuff that gets installed, so it's easy to answer
questions.  Mind you, it changes a lot from day to day, but it's still a
tiny job to update it if I want to take a look.

    Greg