public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Robins Tharakan <robins.t@kutumb.org.in>
To: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: developers and GPL in products (Was: Re: GPL violations by wireless manufacturers)
Date: 25 Jun 2003 06:17:20 +0530	[thread overview]
Message-ID: <1056502051.15687.33.camel@zeus.simple.com> (raw)
In-Reply-To: <200306241727.51092.zack@tehunlose.com>


Therefore, if Company A "sells" the package to anybody outside the
company then it has to "make available" the source, including people
like the primary developer.

But i think the second part of Zack's reply might not be right.
The company A only needs to make "available" the source. it doesnt
"have" to bundle the source with the binaries... (maybe make it
available on the website or make some such provisions...)

robins

On Wed, 2003-06-25 at 05:57, Zack Gilburd wrote:
> On Tuesday 24 June 2003 11:25, Roger Larsson wrote:
> > A customer of a product B that uses GPL project A can
> > require the source for A. But what about the primary developer?
> > Suppose the company charges an obscene amount of money for
> > the product (that might be an enhanced project A, like a patch to allow
> > compilation on Win32) - the primary developer might not afford to buy that
> > product.
> 
> Not exactly.  By my understanding of the GPL, if you plan on distributing 
> binaries outside of your corporation, you MUST make the source available to 
> any and all third parties.  In adition, you must bundle the source code with 
> the binary.
> 
> That's just what I have read from the GPL -- IANAL.
> 
> -- 
> Zack Gilburd
> http://tehunlose.com



  parent reply	other threads:[~2003-06-25  0:33 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-24 10:10 GPL violations by wireless manufacturers vanstadentenbrink
2003-06-24 10:38 ` David Schwartz
2003-06-24 11:20   ` vanstadentenbrink
2003-06-24 18:18     ` David Schwartz
2003-06-24 23:37       ` vanstadentenbrink
2003-06-25  2:42       ` Horst von Brand
2003-06-29  3:14         ` Andre Hedrick
2003-06-24 18:25     ` developers and GPL in products (Was: Re: GPL violations by wireless manufacturers) Roger Larsson
2003-06-24 23:26       ` Krzysztof Halasa
2003-06-25  0:27       ` Zack Gilburd
2003-06-25  0:39         ` Bryan Andersen
2003-06-25  0:41         ` developers and GPL in products (Was: Re: GPL violations by wi reless manufacturers) David Lang
2003-06-25  0:47         ` Robins Tharakan [this message]
2003-06-25  3:21           ` developers and GPL in products (Was: Re: GPL violations by wireless manufacturers) Brian Davids

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=1056502051.15687.33.camel@zeus.simple.com \
    --to=robins.t@kutumb.org.in \
    --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