ity contributed pre-built eggs
but... there is no wiki initialized yet for the project
3/ Announces: we would like to announce on the pylucene-user list the
availability of newly released eggs
Any objections or comments?
--
Cordially
Philippe
philippe ombredanne | 1 650 799 0949 | pombreda
d paths there.
On Jun 2, 2011, at 3:10, Philippe Ombredanne wrote:
could we come at least with a build option to enable this?
The option already exists: when building jcc, you can pass it your own version
of JCC_LFLAGS set as an env variable that overrides the defaults to whatever
you lik
On 2011-06-02 18:26, Andi Vajda wrote:
On Jun 2, 2011, at 3:10, Philippe Ombredanne wrote:
On 2011-06-01 20:54, Roman Chyla wrote:
Note that the
location of the java that was used for the project built will be
hardcoded inside the dynamic library, but I plan to change the header
and set a few
[
https://issues.apache.org/jira/browse/PYLUCENE-10?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Philippe Ombredanne reopened PYLUCENE-10:
-
I would like to reopen this issues on two grounds:
1/ I have started http
hardcoded in the shared object as a hard path to the libs folder, but
also there is an implied dep on setuptools via pkg_resources
So for now, you cannot even build on a jdk and deploy on a jre.
--
Cordially
Philippe
philippe ombredanne | 1 650 799 0949 | pombredanne at nexb.com
nexB - Open by
tches there if you have some?
Building pylucene/jcc is indeed difficult for newcomers.
Indeed too hard imho. A big deterrent. Such that it does likely impair
the project reach, growth and health.
On Wed, Jun 1, 2011 at 10:54 AM, Philippe Ombredanne
wrote:
Howdy!
I think it is way too ha
