Hi!

I downloaded PyLucene 0.98 for Linux (Fedora Core 3) and was
disappointed to see that I couldn't use the binary packages because my
python was built with UCS4 characters and the package assumed UCS2. 
(At least, this is my theory based on the error message and the
resulting web search.)

So I went to build it from source.  A couple comments:

1. I don't want to edit the Makefile.  When I'm building things from
source, I prefer to build them automatically via script so I can
consume new source code by running the same script.  Is there any
reason PyLucene can't use distutils?  It's pretty standard, much more
convenient for the user, and solves problems 2 and 3.

2. I don't want to install the package in the site-packages directory
in my global python package directory, I want to install it in a
special directory where I'm putting all the packages built for my
application.   That way, I don't need to do all this stuff as root. 
With distutils, I could just run
setup.py --home=$MY_BETTER_DIRECTORY
With the makefile, I had to trick it by setting PREFIX_PYTHON=/usr and
then doing
make install PREFIX_PYTHON=$MY_BETTER_DIRECTORY

3. When I build that way, I get warnings about security providers:
>>> import PyLucene
WARNING: could not properly read security provider files:
         file:/usr/lib/python2.4/site-packages/security/libgcj.security
         file:/usr/lib/python2.4/site-packages/security/classpath.security
         Falling back to standard GNU security provider
The .security files are present in the right place relative to the
directory that I installed in, but apparently the wrong paths are
hard-coded somewhere.  Based on what's in these files, I think the
warning doesn't matter, but it'd be nice if whatever gcj was doing
with these files could be configured to be relative to the
installation prefix, which as per 1 and 2 shouldn't have to be the
same as the Python interpreter installation prefix.

_______________________________________________
pylucene-dev mailing list
[email protected]
http://lists.osafoundation.org/mailman/listinfo/pylucene-dev

Reply via email to