I wrote:
Looks indeed like it is sufficient. This should get fixed, Strigi
should
not refuse to run entirely with the Redland backend. That said, I remember
now that in 4.2 prereleases it was crashing somewhere inside RDF-related
code, so maybe that's why they disabled it. (They didn't want to fix the
Redland code so they just disabled it. :-/ )
For reference, here's the crash:
https://bugzilla.redhat.com/show_bug.cgi?id=478509
I think upstream didn't even know about this when they disabled it, it was
just for performance reasons. But it does mean that's another problem we'd
have to deal with if we want to support Strigi on Redland. Sigh...
Kevin Kofler