|
From: Eric B. <eb...@cy...> - 2000-10-19 11:24:52
|
Ali Abdin wrote:
>
> There is a solution to this. Include a patch to the RPM that will
> "modify" the tarball to NOT run scrollkeeper-install (patches can be
> "attached" to RPMS (RedHat does it, but I do not know the technical side
> of how it is done)). This is the only "sound" solution I can think of.
> Debian dudes have their own patches to handle stuff :)
It's no clean solution and it can be tedious to prepare patches.
No the better is to let "make install" behave normally and use somehow
the partial database it built, either by ensuring it is copied in some
common directory but with a different name as the other database
snippets and that the help browser copes with a database spread over
many files, or that it gets merged together with the "real" database on
the user's hard disk. The first solution is the one that requires less
work for the distribution packager.
> Unfortunately, you have to ask yourself - Will application writers want
> to do this for their packages?
--
Éric Bischoff - mailto:eb...@cy...
__________________________________________________
\^o~_.
.~. ______ /( __ )
/V\ Toys story \__ \/ ( V
// \\ \__| (__=v
/( )\ |\___/ )
^^-^^ \_____( )
Tux Konqui \__=v
__________________________________________________
|