When he originally wrote scripts, I was archaically thinking just
of shell scripts. Programming in Perl, Python, and Ruby is much
more like C programming, and the things you do by linking with
libraries in C are done with use, require, and import in
these languages. These are
On Sat, 16 Dec 2006 09:27:20 +0100 (CET)
Alfred M. Szmidt [EMAIL PROTECTED] wrote:
This is clearly a deriviate work, the program changes how it
works if you remove the GPLed library/script/whatever. It also
stops working without the GPLed library/script/whatever.
Factual
Importing is done at run time. [...]
We both are assuming things meant by importing that the OP might not
have meant.
You don't get it - one cannot write a (useful) 'C' program without
a few #include statements (which will cause the preprocessor to
import the header files).
I take
The OP said that his program works without the GPLed scripts:
| [EMAIL PROTECTED] said: These GPL scripts are not necessary
| to use the application, they just add more functionality.
The OP said that they add features that are not provided if the GPLed
scripts are used. This by any
On Sat, 16 Dec 2006 17:19:13 +0100 (CET)
Alfred M. Szmidt [EMAIL PROTECTED] wrote:
Importing is done at run time. [...]
We both are assuming things meant by importing that the OP might not
have meant.
You don't get it - one cannot write a (useful) 'C' program without
a few
On Fri, 15 Dec 2006 01:03:11 +0100 (CET)
Alfred M. Szmidt [EMAIL PROTECTED] wrote:
The scripts of the OP are written by the OP, and contain no code of
the GPLed script.
The program by the OP imports the GPLed script, that is all that
matters.
It is especially asinine because it
On 14 Dec 2006 15:48:30 -0800
[EMAIL PROTECTED] wrote:
Suppose I want to err on the safe side, let's consider for a while
that what I asked before is not allowed.
Does it seem less questionable (or more clearly allowed) for me to
prepare a zip file containing GPL'ed script files and put it
Stefaan A Eeckels [EMAIL PROTECTED] writes:
You don't get it - one cannot write a (useful) 'C' program without a
few #include statements (which will cause the preprocessor to
import the header files). If that makes the source code a
derivative work of the header files, you'd have to ask the
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
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
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.
This is clearly
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
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
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
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
On Fri, 15 Dec 2006 16:05:41 +0100
David Kastrup [EMAIL PROTECTED] wrote:
Stefaan A Eeckels [EMAIL PROTECTED] writes:
You don't get it - one cannot write a (useful) 'C' program without a
few #include statements (which will cause the preprocessor to
import the header files). If that makes
On 13 Dec 2006 15:23:33 -0800
[EMAIL PROTECTED] wrote:
Hello,
My application consists of a collection of scripts (full source
distributed) licensed under a license that I'll call A.
I want to distribute with my application, the source version of a
script licensed under GPL. This script
My application consists of a collection of scripts (full source
distributed) licensed under a license that I'll call A. I want
to distribute with my application, the source version of a script
licensed under GPL. This script (source) will be imported and
used at runtime by my
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
On Thu, 14 Dec 2006 18:03:37 +0100 (CET)
Alfred M. Szmidt [EMAIL PROTECTED] wrote:
My application consists of a collection of scripts (full source
distributed) licensed under a license that I'll call A. I want
to distribute with my application, the source version of a script
The scripts of the OP are written by the OP, and contain no code of
the GPLed script.
The program by the OP imports the GPLed script, that is all that
matters.
It is especially asinine because it makes every source program a
derivative work of the OS or at least the libraries it
Suppose I want to err on the safe side, let's consider for a while that
what I asked before is not allowed.
Does it seem less questionable (or more clearly allowed) for me to
prepare a zip file containing GPL'ed script files and put it as a
separate download on my site (telling the users to unzip
Hello,
My application consists of a collection of scripts (full source
distributed) licensed under a license that I'll call A.
I want to distribute with my application, the source version of a
script licensed under GPL. This script (source) will be imported and
used at runtime by my application.
[EMAIL PROTECTED] wrote:
Hello,
My application consists of a collection of scripts (full source
distributed) licensed under a license that I'll call A.
I want to distribute with my application, the source version of a
script licensed under GPL. This script (source) will be imported and
In article [EMAIL PROTECTED],
Geico Caveman [EMAIL PROTECTED] wrote:
[EMAIL PROTECTED] wrote:
Hello,
My application consists of a collection of scripts (full source
distributed) licensed under a license that I'll call A.
I want to distribute with my application, the source version
25 matches
Mail list logo
