[htdig-dev] Re: mifluz merge snapshot 2002-08-27

[Geoff H. <ghu...@ws...>]

I've posted a revised mifluz-merge snapshot. This version should be much 
more stable and I can confirm that it'll index all of htdig.org 
(including mailing list archives), run htfuzzy, htpurge, htmerge, 
htstat, and htnotify. There's still a memory leak hiding around in 
htsearch, so it often segfaults. Help with leak detection would be 
GREATLY appreciated!

I would hope that at least for indexing, all the bugs are out. Please 
prove me wrong, so we can get this ready for wide-scale release.

This version of ht://Dig is an experimental snapshot of 3.2.0b4 including
a new version of the mifluz backend. With help testing this and beating 
out some bugs, I'll pour it into the main CVS repository. So if you're 
willing to try very bleeding edge code (i.e. may not compile or run 
correctly), some feedback would be very helpful.

The snapshots will be left in <http://www.htdig.org/files/snapshots/> 
but there's no script--I'm rolling them by hand as needed. I doubt I'll 
ever have time to roll more than one a day, so I'm not concerned by the 
date stamp. :-)

If you'd like to give it a spin, please see below, particularly about 
libiconv--which will eventually have to be bundled much like the 
Berkeley DB or how we bundled librx.

-Geoff

CAVEAT LECTOR:
* Some additional software may be required for compilation and/or 
running this
  version. Currently, known requirements are:
   - libiconv: <ftp://ftp.gnu.org/pub/gnu/libiconv/>

  Automake 1.6.3 and Autoconf 2.53 are required for updating/revising 
config and
  Makefiles. Older versions will cause problems in building.

* This version is extremely experimental. Don't blame me if it eats your 
files,
  disks, RAM, OS, etc. I doubt it, but I'm not making any promises.
  (NO WARRANTY EXPRESSED OR IMPLIED.)

* This version has received limited testing, so there are likely tons of 
bugs.
  Please report them to me or htd...@li... so they can 
be squashed.

* Not all features are implemented, e.g. revised documentation, faster 
indexing, faster
   searching lower memory requirements, etc. This will happen shortly. 
Let's fix bugs
   first.