|
From: Dan M. <mu...@al...> - 2002-04-21 04:05:58
|
Mikael, ScrollKeeper 0.3.8 addresses this issue by having a new configure option, --with-omfdirs. Just specify all the paths you want ScrollKeeper to search for OMF files, seperated by colons. These paths will be put in $sysconfdir/scrollkeeper.conf and searched whenever you update or rebuild the database. I expect the build scripts (eg. vicious-build-scripts and Garnome) can be easily updated to configure ScrollKeeper as: ./configure --localstatedir=/gnome/head/INSTALL/var --prefix=/gnome/head/INSTALL --sysconfdir=/gnome/head/INSTALL/etc --with-omfdirs=/gnome/head/INSTALL/share/omf or something of that sort, depending on where you are installing everything. If this doesn't solve the problem for some reason, tell me why not and which paths you'd like put into /etc/scrollkeeper.conf. Dan On 16 Apr 2002, Mikael Hallendal wrote: > tis 2002-04-16 klockan 08.12 skrev Dan Mueth: > > > > ScrollKeeper 0.3.7 is now available. > > Thanks a lot! > > Would it be possible to install the locations from vicious-build-scripts > (/gnome/head/INSTALL/share/oaf) and the default locations for the > various other buildscripts in /etc/scrollkeeper.conf. I see lots of > weird locations in there now so I figure just adding a few extra > shouldn't be a problem? > > Regards, > Mikael Hallendal > > |