On Wed, Jul 3, 2013 at 2:55 AM, Wayne Meissner <wmeiss...@gmail.com> wrote:
> On 3 July 2013 16:31, Charles Oliver Nutter <head...@headius.com> wrote:
>
>> * cext handling?
>
> Kill it! Kill it with fire!
>
> As much as I don't like breaking backward compatibility in a minor
> point release, cext is pretty broken as it stands right now, and if
> the external project is ready to roll, then there is a path forward
> for those who really need it.
The external project is *close* to working. There are a few tasks left
to get it to the point where I feel 3rd parties could maintain it:
* Make it usable from the external repo. Mostly this involves getting
the JNI lib + jar to load properly and be able to load extensions. My
no_cext branch has the removal from JRuby + modification to loading to
make it dynamic, but the external repo doesn't boot properly yet.
* Make it installable as a gem. I'm not sure if this is exactly the
right approach, but what I expect would be that it could gem install,
build the cext JNI extension, install it somewhere JRuby can pick it
up easily, and boot it whenever a cext load is detected.
I mostly need help getting it to boot, since it *does* appear to build
now. If we can get it to boot from the external repo, I'd be
comfortable deleting it from JRuby 1.7.5 release.
- Charlie
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
