Am 27.01.2009 um 14:29 schrieb Yavor Doganov:
[I submitted this as a Trac ticket, but got Submission rejected due
to potential spam or similar.]
I believe Gajim is currently not distributable, as even an optional
dependency on python-openssl requires the license of Gajim to have the
(in)famous
Am 27.01.2009 um 14:48 schrieb Jonathan Schleifer:
d8289
Additionally, GPL explicitely allows mere aggregation, so even our
Windows binaries are no
See also:
http://groups.google.com/group/comp.lang.python/msg/
29c7588fbecproblem, as OpenSSL is a separate DLL which is loaded at
runtime.
On Tue, Jan 27, 2009 at 02:48:45PM +0100, Jonathan Schleifer wrote:
We do not ship with py-OpenSSL.
We do not include any of the code from py-OpenSSL.
I never said you did.
I don't see where we are violating any license.
You are violating your own license, the GPL.
OpenSSL is loaded at
Am 27.01.2009 um 14:56 schrieb Yavor Doganov:
On Tue, Jan 27, 2009 at 02:48:45PM +0100, Jonathan Schleifer wrote:
We do not ship with py-OpenSSL.
We do not include any of the code from py-OpenSSL.
I never said you did.
Then I fail to see the problem.
I don't see where we are violating
Yavor Doganov wrote:
On Tue, Jan 27, 2009 at 02:48:45PM +0100, Jonathan Schleifer wrote:
OpenSSL is loaded at runtime, but GPL doesn't cover which code is
allowed to be run in memory,
Please. All libraries you link against should be under a GPL-compatible
license. The fact that you link
Anfang der weitergeleiteten E-Mail:
Von: Yavor Doganov ya...@gnu.org
The problem is the linking. You can't link a GPL'ed application against
a library under incompatible license, unless it classifies as a system
library.
You can, if you are not DISTRIBUTING the result of the linking. The
