On 20/08/07, Stanislav Brabec <[EMAIL PROTECTED]> wrote: > Michel Salim wrote: > > I'm currently working on packaging a GNOME application that installs > > OMF files, and thus requires scrollkeeper to be run on post-install / > > post-uninstall. > > > > I am getting segfaults, however, which turns out to be because > > /var/lib/scrollkeeper was not present! i.e. the scrollkeeper database > > was never initialized. > > > > This is probably a bug with scrollkeeper (shouldn't it initialize its > > database post-install, and own /var/lib/scrollkeeper?), but should I > > handle this differently, i.e. run a test before running > > scrollkeeper-update? > > AFAIK, in new SuSE versions scrollkeeper is only a build time dependence > and you don't need to call anything in %post/%postun. In old SuSE > versions SuSEconfig was updating the database if a flag file in /var/lib > was created in %post/%postun. > > The segfault you experience is most probably: > https://bugzilla.novell.com/show_bug.cgi?id=258576
It is -- I used exactly the same workaround. Any reason why scrollkeeper is not patched to just own and create /var/lib/scrollkeeper? > > You should not call scrollkeeper in %install phase. But it is not so > easy as it should be: > https://bugzilla.novell.com/show_bug.cgi?id=237140 It was in %postinstall. Should I take it off from there too? If --disable-scrollkeeper is passed to %configure, actually, I might not even need a BR on it. Doesn't yelp require scrollkeeper, though? How do us poor GNOME users get our documentation indexed? :) Many thanks, -- Michel --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
