Licensing terms for "linking" with Ruby

Rafa_F · June 21, 2013, 12:21pm

Hi,

I am interested in knowing what license terms are applicable for
invoking a Ruby script from an external application by linking with Ruby
engine.

To be more specific, following is the list of “functions” I want to
invoke so that my given script can execute inside ruby:

ruby_incpush
ruby_init_loadpath
ruby_set_argv
ruby_script
rb_load_protect
rb_eval_string_protect
rb_obj_as_string

Any pointers/ help will be highly appreciated!!

Regards,
Muhammad

salmanmanekia · June 21, 2013, 5:36pm

Hi,

In message “Re: Licensing terms for “linking” with Ruby”
on Fri, 21 Jun 2013 19:21:41 +0900, “Muhammad Ali S.”
[email protected] writes:
|
|Hi,
|
|I am interested in knowing what license terms are applicable for
|invoking a Ruby script from an external application by linking with Ruby
|engine.

You can treat it under the BSD license.

Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions
are met:

Redistributions of source code must retain the above copyright
notice, this list of conditions and the following disclaimer.
Redistributions in binary form must reproduce the above copyright
notice, this list of conditions and the following disclaimer in the
documentation and/or other materials provided with the distribution.

THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS’’ AND
ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
PURPOSE
ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE
FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
CONSEQUENTIAL
DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
STRICT
LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY
WAY
OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
SUCH DAMAGE.

salmanmanekia · June 27, 2013, 5:43pm

Hi,

On 21 Ιουν 2013, at 18:12 , Muhammad Ali S. [email protected]
wrote:

Hi,

Thanks for the quick response. If am not going to annoy you, may I ask:

How do we know that the response is from Yukihiro himself?

There’s a digital signature I can see there, which you can verify by
third parties. [1]

Muhammad

–
Posted via http://www.ruby-forum.com/.

[1] The GNU Privacy Handbook

Panagiotis (atmosx) Atmatzidis

email: [email protected]
URL: http://www.convalesco.org
GnuPG ID: 0x1A7BFEC5
gpg --keyserver pgp.mit.edu --recv-keys 1A7BFEC5

salmanmanekia · June 21, 2013, 6:12pm

Hi,

Thanks for the quick response. If am not going to annoy you, may I ask:

How do we know that the response is from Yukihiro himself?
Why is GPL license distributed with Ruby? How do we know which
components are GPL based?
When ruby.h is included in a C++ application, almost all header files
from the Ruby distribution get included, and if each one has different
license associated with it, is there a clean way to extract non-GPL
files so that one can link with Ruby in a commercial application?

Regards,
Muhammad

salmanmanekia · June 21, 2013, 6:28pm

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

In message “Re: Licensing terms for “linking” with Ruby”
on Sat, 22 Jun 2013 01:12:11 +0900, “Muhammad Ali S.”
[email protected] writes:

|Hi,
|
|Thanks for the quick response. If am not going to annoy you, may I ask:
|
|1. How do we know that the response is from Yukihiro himself?

You can confirm when you meet me in person.

|2. Why is GPL license distributed with Ruby? How do we know which
|components are GPL based?

Ruby used to be licensed under GPL, the file is kinda left-over. And
you can check LEGAL file to tell which files are under other license
terms.

|3. When ruby.h is included in a C++ application, almost all header files
|from the Ruby distribution get included, and if each one has different
|license associated with it, is there a clean way to extract non-GPL
|files so that one can link with Ruby in a commercial application?

Check LEGAL file. The core Ruby does not have any problem to link
with a commercial application.

          matz.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.9
http://mailcrypt.sourceforge.net/

iEYEARECAAYFAlHEfqIACgkQOP4CaTj5SZffKACdHM7lKPUuqYd0uycNg8BI03qq
0oYAmwWjcpto57nIce22jP312cWenwsd
=Kgx2
-----END PGP SIGNATURE-----

salmanmanekia · June 27, 2013, 5:03pm

Hi Matz,

Thanks for your responses. I have spent reasonable time going through
the LEGAL file (as you suggested), and I can see that enough detail is
provided for each chunk of code that Ruby has borrowed from somewhere
else.

But…

Several of these .h or .c files require copyright notices to be
distributed with the final software, just like you did with the LEGAL
file. However, if I now link with Ruby, is there a clean way to
determine which .h and .c files get included in the .lib file produced
by building Ruby? I only link to the final .lib and it becomes part of
my software. This .lib would include at least “some” of these “other”
license files. How can I find out which ones?

I need to keep the number of copyright notices/ legal bindings to the
minimum.

Any help will be highly appreciated.