Re: Using a script licensed under GPL in an application licensed under a license that's not compatible with GPL

[observatory]

The scripts are in ruby, basically what I do is:

require 'gpl_script'

GplClass.do_work

Similarly in Python I would do:

import gpl_script

GplClass.do_work()

These GPL scripts are not necessary to use the application, they just
add more functionality.

Thanks

Barry Margolin wrote:
> In article <mailman.1887.1166115954.2155.gnu-misc-discuss@gnu.org>,
>  "Alfred M. Szmidt" <ams@gnu.org> wrote:
>
> >    What does it mean to "link against" a script?  Linking is something
> >    you do with compiled programs, not scripts.
> >
> > You can `link' script just fine, for example, you can use the `source'
> > command in bash.
> >
> >    Anyway, it's possible that a case could be made tha his original
> >    plan would fall under the GPL's "mere aggregation" clause, which
> >    allows programs with different licenses to be distributed together
> >    with GPL programs.
> >
> > As long as the program simply does fork/exec, this is true.  But the
> > OP explicitly states that he is `importing' the script into the
> > program.
>
> That's another word that isn't normally used to describe use of scripts,
> so it's not clear what he meant.  I assumed he meant that he's simply
> invoking the script as a command.
>
> --
> Barry Margolin, barmar@alum.mit.edu
> Arlington, MA
> *** PLEASE post questions in newsgroups, not directly to me ***
> *** PLEASE don't copy me on replies, I'll read them in the group ***