Hello, Andi. well, i went ahead and test it on the fresh index built with PyLucene 2.0.
On the debian box it does not optimize, but I downloaded this index on my windows box and it optimized well. I guess I have built wrong way PyLucene on debian... Hm... Here is my config in Debian: VERSION=2.0.0-1 LUCENE_SVN_VER=417135 LUCENE_VER=2.0.0-$(LUCENE_SVN_VER) LUCENE_SVN=http://svn.apache.org/repos/asf/lucene/java/trunk PYTHON_VER=2.4 #DB_VER=4.3.29 DB_VER=4.4.20 PYLUCENE:=$(shell pwd) LUCENE=lucene-java-$(LUCENE_VER) DB_LIB_VER=$(basename $(DB_VER)) # Linux (with gcc 3.4.4 and libgcj statically linked) PREFIX=/usr PREFIX_PYTHON=/usr GCJ_HOME=/usr/local GCJ_LIBDIR=$(GCJ_HOME)/lib #GCJ_STATIC=1 #LIB_INSTALL=libstdc++.so.6 libgcc_s.so.1 #DB=$(PYLUCENE)/db-$(DB_VER) #PREFIX_DB=$(PREFIX)/BerkeleyDB.$(DB_LIB_VER) #ANT=ant PYTHON=$(PREFIX_PYTHON)/bin/python2.4 Is it correct? -- Yura Smolsky, http://altervisionmedia.com/ _______________________________________________ pylucene-dev mailing list [email protected] http://lists.osafoundation.org/mailman/listinfo/pylucene-dev
