Currently its going to be LGPLv3. Thats mostly so I can easily borrow code from e.g. JNA if/when I need to to flesh out its capabilities - otherwise I will have to reinvent the wheel, and I'm lazy, so I don't like having to do extra work unless I have to. The aim of JFFI was performance vs JNA, not a licensing change.
Of course, a gym bag full of cash is always useful in persuading me to do the extra work and change the license to whatever is most convenient. JFFI in jruby isn't a short term solution anyway - its not going to go in until after the alleged branching off of jruby-2.0 (aka JRuby-Forever :) We really need to make JRuby _not_ depend on native code, since there are platforms like OpenBSD, NetBSD, FreeBSD, etc that would require jna-posix and JNA/JFFI to be ported to them, and that will become a huge PiTA overhead if we had to support each one with native code. 2008/8/4 Matt Fletcher <[EMAIL PROTECTED]>: > Wayne, if you're out there reading this, what kind of license are you > planning on for JFFI? > Charles: I'll stay in touch in IRC when it comes time to start severing JNA > from JRuby. > > On Sun, Aug 3, 2008 at 8:39 PM, Charles Oliver Nutter > <[EMAIL PROTECTED]> wrote: >> >> These are largely questions for Wayne, since JFFI is his baby. If he'd >> willing to add a more BSD/MIT-like license it might solve your long term >> issues. >> In the short term, we ought to look at a way to decouple JNA from JRuby >> proper. Much of that has already been done through the jna-posix project, >> which would only take a little work to rewire to fall back on the Java-based >> impl when JNA isn't present. But there are also other places we use JNA >> inside JRuby that should probably be made to fall back or disable themselves >> when JNA isn't present. UNIX sockets come to mind, for example. >> >> - Charlie >> >> --------------------------------------------------------------------- >> To unsubscribe from this list, please visit: >> >> http://xircles.codehaus.org/manage_email >> >> > > --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
