From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: riel@conectiva.com.br (Rik van Riel)
Cc: cfriesen@nortelnetworks.com (Christopher Friesen),
linux-kernel@vger.kernel.org
Subject: Re: Somewhat different GPL Question
Date: Fri, 27 Oct 2000 21:49:44 +0100 (BST) [thread overview]
Message-ID: <E13pGRe-0004pR-00@the-village.bc.nu> (raw)
In-Reply-To: <Pine.LNX.4.21.0010271604360.25174-100000@duckman.distro.conectiva> from "Rik van Riel" at Oct 27, 2000 04:06:23 PM
> If you're making interprocess calls to call the GPL code,
> I suspect you won't have to make your code GPL.
>
> OTOH, if you /link/ against a GPL shared library, you will
> have to GPL the source of your program (that is, you'll have
> to give it to the people who receive the binary from you).
The out of court settlements don't actually bear up to this interpretation
and have been more about 'depending on' as a definition for linking and what
is and is not an entire application.
Its one reason Im glad Linus had the sense to put an explicit statement about
syscalls in the kernel COPYING file.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-10-27 20:55 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-27 16:36 GPL Question Jason Wohlgemuth
2000-10-27 16:31 ` David Weis
2000-10-27 17:21 ` Alan Cox
2000-10-27 17:26 ` Matthew Dharm
2000-10-27 17:56 ` Somewhat different " Christopher Friesen
2000-10-27 18:06 ` Rik van Riel
2000-10-27 20:49 ` Alan Cox [this message]
2000-10-27 17:16 ` Mark Salisbury
2000-10-27 17:23 ` Alan Cox
2000-10-27 18:53 ` David Schwartz
2000-10-27 18:56 ` Rik van Riel
2000-10-27 20:53 ` Alan Cox
2000-10-27 19:17 ` James Sutherland
2000-10-27 21:08 ` Brian F. G. Bidulock
2000-10-27 20:52 ` Alan Cox
2000-10-30 12:27 ` Helge Hafting
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E13pGRe-0004pR-00@the-village.bc.nu \
--to=alan@lxorguk.ukuu.org.uk \
--cc=cfriesen@nortelnetworks.com \
--cc=linux-kernel@vger.kernel.org \
--cc=riel@conectiva.com.br \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.