I'm quite sure that this means that code that's licensed under the ruby license can be relicensed under the gpl, but not the other way around, ie. (l)gpl code cannot be relicensed under the ruby license. For example, the BSD license is said to be compatible with the GPL aswell, but that surely doesn't mean that any gpl code can be relicensed as bsd licensed code.
As for glib, it's lgpl, so it's no problem to dynamically link to it, from code that's licensed under the ruby license, but modifying, and/or relicensing glib under the ruby license is probably not allowed. Greets, Lieven van der Heide On 8/27/07, Nikolai Weibull <[EMAIL PROTECTED]> wrote: > Hi! > > I have written a library [1] that is currently under consideration for > (at least partial) inclusion in Ruby 2.0 [2]. I used GLib as a > reference implementation while writing this library and I am thus > wondering exactly how licensing works in this situation. > > GLib is released under the LGPL and Ruby is released under its own > license [3]. According to the Wikipedia entry [4], the FSF has > claimed that: "This is a Free Software license, compatible with the > GPL via an explicit dual-licensing clause." [5] > > I thus wonder if there is any issue in including code based on [6] > code in GLib in a project licensed under the Ruby license. > > Thanks! > > nikolai > > [1] http://git.bitwi.se/?p=ruby-character-encodings.git;a=summary > [2] http://www.ruby-lang.org/en/ > [3] http://www.ruby-lang.org/en/LICENSE.txt > [4] http://en.wikipedia.org/wiki/Ruby_License > [5] http://www.gnu.org/philosophy/license-list.html#GPLCompatibleLicenses > [6] For some value of "based on", I suppose > _______________________________________________ > gtk-devel-list mailing list > [email protected] > http://mail.gnome.org/mailman/listinfo/gtk-devel-list > _______________________________________________ gtk-devel-list mailing list [email protected] http://mail.gnome.org/mailman/listinfo/gtk-devel-list
