On Wed, 14 Oct 2009, Christian Heimes wrote:
Andi Vajda wrote:
That's great !
I'm not sure what the policy is for posting links to external binaries
on the site but if you send these links to the list, at least people
would be able to find them.
How about you register "pylucene" on PyPI and give me upload permission?
You'd be the owner of the package on the package index but I can provide
the binaries on an official and easy_install-able site.
Hmm, that's an idea...
It is my understanding that for a package to 'work' in PyPI it needs to have
some setup.py support, right ? JCC, for example, is already on PyPI since
it's entirely built with setup.py.
PyLucene, on the other hand, does not have a setup.py file, it relies on JCC
and 'make' to provide this functionality. If JCC became a
distutils/setuptools 'compiler', using setup.py to do a PyLucene build might
become easier.
Even in a distribution that included binaries, setup.py would be needed to
install them. For Windows binaries this would be most welcome for many
reasons. For other systems, in particular those where the path to the libjcc
shared library (shared mode) is linked into the executables depending on
it (using -rpath or -R), such a binary install might become more
problematic.
But maybe I'm misunderstanding how this works. Do you already have
easy_install'able binary distributions for PyLucene on Windows ?
With setup.py ?
If so, are they dependent on another binary distribution of JCC itself which
PyLucene depends on but includes in its sources ? I'd imagine that in a PyPI
distribution scenario, PyLucene would _not_ include JCC but would list it as
a dependency instead.
As a matter of fact, we could experiment with this right away with JCC since
it is already listed on PyPI (in source only).
What do I need to do to give you upload permissions ? What's your account on
PyPI ?
Thanks !
Andi..
