Hi David,

David Pratt wrote:
> Hi Julian. Thanks for your replies. I can split the rss into its own
> package but I will need a svn account. 

Great. I'll send you the credentials during the week-end.

> I'll make the separate package
> nuxeo.rsslucene and make license ZPL so it can work for both. I'll
> modify the trunk of nuxeo.lucene to import the new package instead of
> nxlucene.rss. I can look for any dependencies in NXLucene for the rss
> package and modifiy these on the trunk if you would also like this.

right sounds good. I think I would use svn:externals myself.

> I'll fix the typos also in nuxeo.lucene while I am at it. 

right.

> Are you
> concerned about updating for pyLucene 2.0.x. pyLucene 2.0 has been
> around for a while now. It is looking more promising for builds to work
> on gcc 4.1.0. I had built successfully built an ealier pyLucene on
> FreeBSD a while back but had some trouble trying to build latest but am
> going to try again on a newer FreeBSD version and newer gcc. I kept my
> notes around from the first time. Many thanks.

Of course. Once you got the account feel free to do a branch and migrate
it to PyLucene 2.0. That would be definitely great. I checked a bit.
some part of the Field API I was using with the 1.9.x version of Lucene
has been deprecated on the 2.x branch. So there is a little bit of work
here I guess.

I didn't personally succeed, couple of weeks ago, to run a working
4.1.0, nor the trunk compiled versions of GCC with PyLucene. But Andi
from the OSAF seems to succeed in doing that.

If you need help I'll be around looking a little bit more often at the
list than those past weeks...

Regards,

        J.

P.S : Are you using NXLucene yourself at the moment ?

> Julien Anguenot wrote:
>> Hi David,
>>
>> David Pratt wrote:
>>> Hi. I am just checking out the nuxeo.lucene (ZPL) package but noticed a
>>> dependency on nxlucene (LGPL) for two imports in catalog.py:
>>>
>>> around line 37:
>>>
>>> from nxlucene.rss.resultset import ResultSet
>>> from nxlucene.rss.adapter import PythonResultSet
>>>
>>> The nxlucene.rss package is a small package with no dependencies on
>>> nxlucene.
>>
>> Yes. This is a NXLucene package dependency.
>>
>>> I would very appreciate it if this package could be brought into the
>>> nuxeo.lucene package so that there are no parts that are not ZPL - since
>>> I work with ZPL pretty much exclusively.
>>
>> right. I don't see any blocker for that.
>>
>>> Alternatively, if this sub package is needed by both packages, perhaps
>>> it could be split out under the ZPL so it could remain in common without
>>> affecting the license of nuxeo.lucene.
>>
>> yes. this is the thing to do but you'll do the package split your self
>> :) Do you have an svn account ?
>>
>>> Of course, it would be great if you could consider ZPL for nxlucene also
>>> - to make these two packages consistently licensed - which would also
>>> make me a happy camper. :-)
>>
>> Nope. NXLucene will remain under the LGPL.
>>
>> Cheers,
>>
>>     J.
>>
> 


-- 
Julien Anguenot | Nuxeo R&D (Paris, France)
Open Source ECM - http://www.nuxeo.com
Nuxeo 5 : http://www.nuxeo.org
Mobile: +33 (0) 6 72 57 57 66

Attachment: signature.asc
Description: OpenPGP digital signature

_______________________________________________
cps-devel mailing list
http://lists.nuxeo.com/mailman/listinfo/cps-devel

Reply via email to