From: "David Schwartz" <davids@webmaster.com>
To: "Giuliano Pochini" <pochini@shiny.it>
Cc: <linux-kernel@vger.kernel.org>
Subject: RE: License question
Date: Mon, 19 Jan 2004 03:31:02 -0800 [thread overview]
Message-ID: <MDEHLPKNGKAHNMBLJOLKMEJCJKAA.davids@webmaster.com> (raw)
In-Reply-To: <XFMail.20040119122403.pochini@shiny.it>
> On 17-Jan-2004 David Schwartz wrote:
> >> > - Redistributions of source code must retain the above copyright
> >> > notice, this list of conditions and the following disclaimers.
> > Sorry, that's an "additional restriction" not permitted
> > under the GPL.
> These are in fact the points I wished your opinion about...
> Actually these are requirements (like others said), not
> use restrictions.
There is no difference. Every requirement can be rephrased as an equivalent
restriction. The requirement that you maintain the terms is the same as a
restriction against removing them.
> btw, IANAL and IP rights are a minefield.
Definitely.
> Since their code is C++ I already rewote everything in C, but it
> also contains the binary firmwares which I can't rewrite. That's
> why I asked you about the license.
Then you have another problem. You can't place something under the GPL if
you don't have the source code to it. How can you offer the source code to
others if you don't have it? (Though my opinion seems to differ from the
mainstream on this point. It is my opinion that you must possess the source
code to any object code you wish to GPL.)
> It's likely Echoaudio will change the license in the next release
> to a dual GPL/custom license, so this will be no more an issue.
Glad to hear that.
> Thanks for you answers.
Of course, you shouldn't rely upon them.
DS
next prev parent reply other threads:[~2004-01-19 11:31 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-17 18:57 Giuliano Pochini
2004-01-17 19:25 ` Valdis.Kletnieks
2004-01-18 9:27 ` Sergey Vlasov
2004-01-17 19:41 ` Misshielle Wong
2004-01-17 22:06 ` David Schwartz
2004-01-18 17:23 ` Misshielle Wong
2004-01-19 8:14 ` Jes Sorensen
2004-01-19 16:00 ` J. Bruce Fields
2004-01-19 17:03 ` Misshielle Wong
2004-01-19 11:24 ` Giuliano Pochini
2004-01-19 11:31 ` David Schwartz [this message]
2004-01-20 9:30 ` Giuliano Pochini
2004-01-20 17:19 ` David Schwartz
2004-01-19 12:15 ` Jes Sorensen
2004-01-18 11:07 ` Andreas Jellinghaus
[not found] <MDEHLPKNGKAHNMBLJOLKEEEIJKAA.davids@webmaster.com>
2004-01-18 21:54 ` Misshielle Wong
[not found] <MDEHLPKNGKAHNMBLJOLKKEFLJKAA.davids@webmaster.com>
2004-01-19 0:25 ` Misshielle Wong
[not found] <MDEHLPKNGKAHNMBLJOLKAEGJJKAA.davids@webmaster.com>
2004-01-19 4:17 ` Misshielle Wong
2004-01-19 10:05 ` David Schwartz
2004-01-22 7:37 ` David Meybohm
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=MDEHLPKNGKAHNMBLJOLKMEJCJKAA.davids@webmaster.com \
--to=davids@webmaster.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pochini@shiny.it \
/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
all inboxes | Powered by JetHome®