From: Krzysztof Halasa <khc@pm.waw.pl>
To: Roger Larsson <roger.larsson@skelleftea.mail.telia.com>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: developers and GPL in products (Was: Re: GPL violations by wireless manufacturers)
Date: 25 Jun 2003 01:26:59 +0200 [thread overview]
Message-ID: <m31xxjuke4.fsf@defiant.pm.waw.pl> (raw)
In-Reply-To: <200306242025.27761.roger.larsson@skelleftea.mail.telia.com>
Roger Larsson <roger.larsson@skelleftea.mail.telia.com> writes:
> 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.
There is no problem with that. Still, the company may choose not to
release the product at all. But, if it does, anyone (any customer)
can make that software public, as permitted by the license.
--
Krzysztof Halasa
Network Administrator
next prev parent reply other threads:[~2003-06-25 23:04 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 [this message]
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 ` developers and GPL in products (Was: Re: GPL violations by wireless manufacturers) Robins Tharakan
2003-06-25 3:21 ` 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=m31xxjuke4.fsf@defiant.pm.waw.pl \
--to=khc@pm.waw.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=roger.larsson@skelleftea.mail.telia.com \
/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