Markus.Herb(a)de.TRUMPF.com wrote:
i've allready asked the following questions.
But the topic of the other thread doesn't fit anymore.
I've downloaded the nightly tarball since my company's firewall doesn't
allow me to use a CVS client.
I found out that the sourcefiles had added a ",v" to each extension like
cs,v and also contained some versioning info.
So I renamed them and deleted the versioning info.
This is not a supported or end-user ready product; you should probably
not attempt to use it unless you know a lot more about it than you
indicate. If you are having trouble getting files out of CVS, this
software IS NOT READY for you and you should not attempt to use it.
If you need to get the source, you should use a CVS client -- the CVS
repository snapshots are copies of the *repository* itself, not of the
current contents. You can google up documentation on various CVS clients
for Windows easily enough.
I have also searched for the libraries and copied them
into
\wikipedia\mwsearch\libs\
I've downloaded and installed mono.
But now I don't know how to compile it. The sources ought to be builded
with monodevelop.
There is a Makefile, which should work with GNU make. It is designed to
run on Linux/Unix and there is no support for Windows. If you have
difficulty writing an alternate build script, this software IS NOT READY
FOR YOU.
Since I'm using Windows XP, I don't know how
to proceed.
The search code in its current state is not a supported product, and I
recommend against trying to use it as is, particularly if you're
uncertain what to do with the code. There is no known support for
running on Windows (it might work, god knows; never been tested).
I really want this Wikipedia search engine up and
running.
Unless you know what you are doing and are working on developing the
lucene search engine itself, I strongly recommend you use MediaWiki's
built-in search that uses MySQL's fulltext search engine.
This is not a supported or complete product. It is not ready for
third-party use. It's barely ready for our own use. There are known
serious problems with the updater. DO NOT ATTEMPT TO USE IT.
-- brion vibber (brion @
pobox.com)