Simon McVittie s...@debian.org writes:
On 07/03/12 09:01, Simon Josefsson wrote:
I co-maintain the libidn package. As upstream, I recently relicensed it
from LGPLv2+ to GPLv2+|LGPLv3+.
This effectively means: recipients of the new libidn may choose any
license which they could choose for
Simon Josefsson si...@josefsson.org writes:
Kalle Olavi Niemitalo k...@iki.fi writes:
I believe GPLv2+|LGPLv3+ is incompatible with
GPLv2|OpenSSL-linking-exception, used in ekg2.
Thank you for a good data point. I've brought this up with
licens...@gnu.org to hear what they have to say
Kalle Olavi Niemitalo k...@iki.fi writes:
Simon Josefsson si...@josefsson.org writes:
Kalle Olavi Niemitalo k...@iki.fi writes:
I believe GPLv2+|LGPLv3+ is incompatible with
GPLv2|OpenSSL-linking-exception, used in ekg2.
Thank you for a good data point. I've brought this up with
* Kalle Olavi Niemitalo k...@iki.fi [120309 13:11]:
On second thought, if a program is licensed under GPLv2 with an
additional permission to link with OpenSSL, this permission does
not survive linking with LGPLv2 libraries either, such as glibc
or libidn before your relicensing. (The reason
Kalle Olavi Niemitalo k...@iki.fi writes:
Simon Josefsson si...@josefsson.org writes:
I have looked at licenses of reverse dependencies, and I did
found some GPLv2-only packages. That caused me to dual license
the package instead of going to LGPLv3+. (GPLv2-only and
LGPLv3+ are
On 07/03/12 09:01, Simon Josefsson wrote:
I co-maintain the libidn package. As upstream, I recently relicensed it
from LGPLv2+ to GPLv2+|LGPLv3+.
This effectively means: recipients of the new libidn may choose any
license which they could choose for the old libidn, except for the
LGPLv2 and
Simon Josefsson si...@josefsson.org writes:
I have looked at licenses of reverse dependencies, and I did
found some GPLv2-only packages. That caused me to dual license
the package instead of going to LGPLv3+. (GPLv2-only and
LGPLv3+ are incompatible.) I am not aware of any other license
7 matches
Mail list logo