On Sat, 4 Feb 2006, Jeff Breidenbach wrote:
The gcj situation is more serious. No way in hell can we package the gcj
runtime inside the PyLucene package. As far as I can tell this is a
showstopper,although I'm curious what the gcj package maintainers have to
say about the matter.
Ah, if only I could statically link _PyLucene.so and libgcj.a, but that I've
never been able to do. On Windows, this is the only way to get an executable
and _PyLucene.pyd is only 4Mb in size. Lucene only needs a small portion of
libgcj.
- help make sure the right people have the right information. Is Andi in good
contact with the Swig authors already? Do they need more detailed
bug reports?
I got a set of patches that solve the issues on swig 1.3.27 from Robin Dunn,
the wxPython maintainer, another big SWIG user (and contributor). I expect his
patches to make it into the SWIG codebase in the near future. From what I've
heard, though, the upgrade to 1.3.28 is going to be more difficult as a number
of changes are in progress for that release.
- I noticed the package is only valid for python-2.4. Most Debian python
packages support multiple versions of python. Maybe this is something
to work on while other paths are blocked?
I have no interest in supporting older versions of python. Python 2.3 has had
a threading bug fixed that seems important enough. I believe this bug fix made
it into Python 2.3.5, if in 2.3 at all.
- See if our counterparts in RedHat, Gentoo, Suse, etc. have made progress
on any of these issues. (Unlikely, I suspect otherwise Andi would know about
it).
I only know of the Debian attempt. I build PyLucene on gentoo regularly, and
it works fine, but the problems are the same: requirements are gcj 3.4.x (x >=
3), Python 2.4, SWIG 1.3.24.
Andi..
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
