This is the mail archive of the guile@cygnus.com mailing list for the guile project.
| Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
|---|---|---|
| Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Who is violating the GPL in this situation? There are three parties
involved, the user loading the library at runtime, the author of
the GPL'd library, and the author of the proprietary application.
The author of the application, who writes the code of that application
to presuppose linking with a specific GPL-covered library, is
violating the terms of use of that library. It doesn't matter whether
the linking is done statically or dynamically.
This only leaves the author of the proprietary app that links against
Guile. This would make the GGPL functionally worthless, since Guile
can link in any library at runtime using the Guile `dynamic-link'
procedure.
Sorry, I cannot make any sense of that sentence. How did Guile com
into this? The scenario I thought we were talking about is that a
proprietary program uses dynamic linking to call a GPL-covered
library.
I don't know what scenario you are talking about now.
So I cannot be sure whether I would agree or disagree
with what you mean to say about it. I suggest that if you
want to write something and have me be able to follow it,
you should start by stating clearly the scenario, and then
write in a more plodding and clear fashion.