The following message is forwarded on behalf of
Marvin Humphrey, a main developer of KinoSearch.

--
best regards,
Randy Kobes


---------- Forwarded message ----------
Date: Sun, 16 Apr 2006 16:37:49 -0700
From: Marvin Humphrey <[EMAIL PROTECTED]>
To: Randy Kobes <[EMAIL PROTECTED]>
Subject: A PPM for KinoSearch

Hello Randy,

A thread on the ActivePerl list regarding build problems with KinoSearch has been brought to my attention. Please forward this message to that list, as several attempts to subscribe via the web interface have failed to produce a confirmation email.

I would very much like to resolve the KinoSearch installation issues on Win32, and a developer's release has been uploaded to CPAN which will hopefully go a long way towards that goal.

The dependency on Sort::External has been eliminated, so that's no longer an issue. It still depends on two other XS modules from CPAN: the ubiquitous Clone, which passes everywhere, and Lingua::Stem::Snowball, which I maintain. Lingua::Stem::Snowball seems to be doing OK, according to <http://ppm.activestate.com/BuildStatus/5.8-L.html>. There are three apparent failures, all on HPUX. One is unlinked so I can't see what's wrong. Another looks like it actually passed to me. The third is apparently due to its dependency on Module::Build. I'm not fixing that! :)

That leaves the compilation problems in KinoSearch itself. Version 0.09, released Thursday, fixes all the trivial variable declaration issues (in addition to implementing incremental indexing and doubling indexing speed :) ). There is one known issue outstanding, which you refer to as "an incorrect number of arguments to the read() function". The real problem seems to be there is a struct which has a member which is a pointer to function, and this member is named "read". That's legal on the three boxes I develop on (Mac OS X 10.4.6, FreeBSD 5.3, RedHat 9), but chokes MSVC. I meant to fix this for 0.09 but it got lost in the shuffle; the name of that struct member has been changed in 0.10_01, so that problem should be going away.

I would very much appreciate it if someone with a Windows box can test 0.10_01, and send their results either to me directly or to the kinosearch mailing list (subscription info at <http://www.rectangular.com/mailman/listinfo/kinosearch/>). To run the test suite via the CPAN shell, type this at the prompt:

  cpan> test CREAMYG/KinoSearch-0.10_01.tar.gz

Another participant in the thread mentioned KinoSearch's "alpha" status. This is true, and KinoSearch is going to keep its "alpha" label for a little while yet. This is primarily because there are some file format design issues yet to be resolved. Maybe it will use the same file format as Java Lucene, maybe not. That would be desirable, but it's actually easier for me to fix Java Lucene than it is to ape its current non-Unicode-compliant behavior using Perl/C. I'm working on that.

In the meantime, I'm reserving the right to tweak the API some. It might not be the best idea to set up and forget a KinoSearch search app right now, but if you have control over which modules get installed and when on your system, things seems to be working out well: <http://www.rectangular.com/kinosearch/benchmarks.html>.

Cheers,

Marvin Humphrey
Rectangular Research
http://www.rectangular.com/
_______________________________________________
ActivePerl mailing list
[email protected]
To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs

Reply via email to