On Sat, 16 Feb 2008, Bill Janssen wrote:
Please note that this build is for Python 2.4, Java 1.6. It will most likely
not work with different combinations of Python and Java.
I'm curious about whether it's possible to distribute Windows binaries
for JCC PyLucene and have them work, considering the variety of Java
installs that are available. I'm thinking about Java 1.5 vs 1.6, and
the various "flavors" of each (jre-1.6.0_02 vs jre-1.6.0_04, for
instance). Many Windows users need to continually upgrade their Java
installs, due to organizational requirements, to track security
updates. (I'm assuming that we hold the version of Python constant.)
This is also an issue for Linux and OS X, but of lesser concern. In
the case of Linux, the environment seems to be so chaotic that it's
essentially impossible to issue a "standard" binary, so the problem
has to be addressed by the end user or the platform packaging system.
In the case of OS X, the changes are so coarse-grained and slow-moving
that the issues seem manageable.
The one thing I know for sure is that Python only guarantees binary
compatibility between major releases. In other words binaries built on 2.4
are not expected to work on 2.5. But binaries built on 2.4.3 are expected to
work with 2.4.4.
I'm not sure whether the same is true with different Java SDK's as long as
they come from the same supplier. Is a binary built with Sun JDK 1.5
expected to run with Sun JRE 1.6 ? I don't know.
I know that PyLucene can be built on Python 2.3.5 - thanks to your
vigilance :) - Python 2.4 and Python 2.5. These versions can then be
combined with Sun Java 1.4, 1.5 and 1.6, openjdk 1.7, Apple Java 1.4 and
1.5. And then, most of these combinations can be built on various Linux
distros 32 and 64-bit, Windows, various Mac OS X releases, ppc and intel,
now Solaris (x86_64 so far), and others I now forget such as FreeBSD, etc...
As you can see - and as you can remember in the gcj-PyLucene days - to do a
fair job at distributing binaries would require quite a build farm and quite
some time. This is why I'm perfectly happy with adding links to the PyLucene
homepage to messages in the pylucene-dev mailing list archives about someone
offering binaries for their favorite OS/CPU/Python/Java/PyLucene combo up
for download.
In any case, since building jcc-PyLucene from sources is so much easier than
building the now deprecated gcj-PyLucene, I'd like to move away from myself
setting any expectations as to shipping any binaries whatsoever.
Andi..
_______________________________________________
pylucene-dev mailing list
[email protected]
http://lists.osafoundation.org/mailman/listinfo/pylucene-dev
