On Thu, 2019-03-21 at 13:17 +0100, Ansgar Burchardt wrote:
> Git in Debian actually links (L)GPL-3+ libraries:
>
> /usr/lib/git-core/git-remote-https links libtasn1.so.6; libtasn1.so.6
> is distributed under non-trivial terms (according to its Debian
> copyright file):
>
On Thu, 2019-03-21 at 10:04 +0100, Florian Weimer wrote:
> * Ansgar Burchardt:
>
> > People have argued before that this applies to Debian. In that
> > case
> > Debian wouldn't be able to distribute binaries of GPL-2-only
> > programs
> > linking against
Paul Jakma writes:
> On Wed, 20 Mar 2019, Ole Streicher wrote:
>> #include
>> int main(void) { zlog_rotate(); return 0; }
>>
>> is not an adaption of any GPL code. It is fully written by my
>> own.
>
> It is written by you, and you have copyright in it (in some way, I
> have the vague idea there c
Dear debian-legal@,
suppose I compile the following trivial GPL-2-only program:
+---
| #include
| int main() { throw std::exception(); }
+---
Then the resulting binary program links (among other things) against
libstdc++6, licensed under GPL-3+ with runtime exception.
The GPL requires the comp
On 07/11/2013 14:15, Paul Wise wrote:
> On Thu, Jul 11, 2013 at 6:29 PM, Lars Meyser wrote:
>> No I did not miss that, but I'm not entirely sure of the implications. So if
>> I
>> use a packaged version of a program which has been modified (e.g. by Debian
>> patches) I am not obliged to make the s
5 matches
Mail list logo