I've packaged the current PyLucene. It's very preliminary, there are tons to things to adjust, highly untested, etc. etc. It's in http://www.jab.org/pylucene with an AMD64 build done on Ubuntu Gutsy.
Quick questions: Is there a good way to get jcc source separate from PyLucene? That's helpful as I need build those two packages separately due to the dependency between them. Currently I'm just slicing and dicing the pylucene tarball. There's a bit in setup.py in jcc, where one has to switch things around if one is on AMD64 linux2 vs. i386 linux2. Is there any way to make that automatic? This would be helpful for autobuilders and I don't know enough python to pull it off. Patch appreciated; no need to put this in the canonical source release. I'm sure I'll have more questions, but that's it for now. Feel free to critique. Not recommended for actual use at this point. Once we get a little cleaner I'll upload into Debian and then PyLucene should percolate through a bunch of Linux distributions. _______________________________________________ pylucene-dev mailing list [email protected] http://lists.osafoundation.org/mailman/listinfo/pylucene-dev
