On Sat, Jun 5, 2010 at 9:08 AM, Ola Bini <ola.b...@gmail.com> wrote: > On 2010-06-02 20.33, Ketan Padegaonkar wrote: >> >> Hi, >> >> IMNAL, but these things rang bells in my head, so I thought I'd ask here. >> >> I'm a committer at eclipse.org wanting to use/depend on (and distribute >> jruby) from the eclipse.org servers, as part of the IP process I noticed >> that jruby v1.5.0 is distributing GPL code which may cause issues to >> downstream consumers. >> >> The file(s) under question are: >> ./lib/ruby/gems/1.8/gems/ruby-debug-base-0.10.3.2-java/lib/linecache.rb >> >> What is interesting is that ruby-debug-base is distributed under an MIT >> license, which *I think* is a violation of GPL under which linecache.rb >> is distributed! >> >> ruby-debug seems to have a dependency on columnize gem which is also GPL >> (and distributed with jruby). >> >> I'm not sure if it means that JRuby must distribute itself under GPL, >> just saying :-) >> > > Hi, > > IANAL either. > > I took a look at this, and it indeed looks a bit bad. As you say, > ruby-debug-base should probably not be MIT with GPL inside of it. And we > shouldn't distribute a GPLed gem inside of JRuby. > > Not sure what the best approach is for now. Can we just remove that gem for > the next release? Do we depend on it in many places? And would it be OK if > we removed the gem while sorting out this issue?
Well I think it is fine if we distribute gems under additional licenses including GPL. I would liken this to the fact that GPL Linux kernels are distributed along with non-GPL code (applications/libraries). ruby-debug-base is not neccesary for JRuby functioning so it is an external add-on. So my argument is that our src and bin releases of JRuby is a full distribution akin to a Linux distro. Maybe we just need to list this with all our other licenses we list at the top? The fact that the gem itself has a violation is something that should be addressed. Has anyone contacted maintainers of jruby-debug-base? We should do due dilligence and get them to correct the issue. For what it is worth I think we can hack out an API-compatible linecache in a few hours if anyone has the time? Can someone do a rainy Saturday project and contribute back a non-GPL linecache to this gem (the API looks pretty small)? You would be a hero and get a beer from me the next time I see you.... -Tom -- blog: http://blog.enebo.com twitter: tom_enebo mail: tom.en...@gmail.com --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
