From: "Christopher Friesen" <cfriesen@nortelnetworks.com>
To: unlisted-recipients:; (no To-header on input)@pop.zip.com.au
Cc: linux-kernel@vger.kernel.org
Subject: Somewhat different GPL Question
Date: Fri, 27 Oct 2000 13:56:23 -0400 [thread overview]
Message-ID: <39F9C1C7.BDEFE414@nortelnetworks.com> (raw)
In-Reply-To: <Pine.LNX.4.10.10010271130550.23907-100000@catbert.desm.plconline.com> <E13pDC5-0004g7-00@the-village.bc.nu> <20001027102645.B28279@one-eyed-alien.net>
If I use some GPL'd code and make calls from my software to the GPL'd
code, do I need to make *my* code available? Or would I only have to
make available any changes to the GPL'd code?
Section 2.b of the GPL seems to indicate that I need to make the source
for my entire executable available if it incorporates any GPL'd source,
and that I cannot charge for the software, only for its distribution.
Is this correct?
Thanks,
Chris
--
Chris Friesen | MailStop: 043/33/F10
Nortel Networks | work: (613) 765-0557
3500 Carling Avenue | fax: (613) 765-2986
Nepean, ON K2H 8E9 Canada | email: cfriesen@nortelnetworks.com
-
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 18:00 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 ` Christopher Friesen [this message]
2000-10-27 18:06 ` Somewhat different " Rik van Riel
2000-10-27 20:49 ` Alan Cox
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=39F9C1C7.BDEFE414@nortelnetworks.com \
--to=cfriesen@nortelnetworks.com \
--cc=linux-kernel@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox