From: "David Schwartz" <davids@webmaster.com>
To: <pjvenda@rnl.ist.utl.pt>, <linux-kernel@vger.kernel.org>
Subject: RE: GPL Violation of 'sveasoft' with GPL Linux Kernel/Busybox + code
Date: Mon, 8 Nov 2004 12:53:22 -0800 [thread overview]
Message-ID: <MDEHLPKNGKAHNMBLJOLKGECMPKAA.davids@webmaster.com> (raw)
In-Reply-To: <418F890D.5070404@rnl.ist.utl.pt>
> if that's the case, isn't it necessary to distribute the proprietary
> parts separately (or vice-versa)? else those proprietary parts would
> also be under the GPL.
It depends what you mean by speparately. RedHat ships CDs that contain both
GPL'd and non-GPL'd packages. They're even tweaked to work together. It
comes down to whether the the thing they're shipping is a single work or a
collection of works, and to what extent you can draw the line between them.
I don't know enough about sveasoft's packaging to say.
However, one thing is clear. If they actually modify source files that
started out as GPL'd works, and then ship the executables, they are
definitely shipping a single work that is a derivative of the GPL'd work.
DS
next prev parent reply other threads:[~2004-11-08 21:05 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-07 17:27 Shawn Starr
2004-11-07 19:33 ` Raphaël Rigo LKML
2004-11-07 19:38 ` Shawn Starr
2004-11-07 21:16 ` Daniel Egger
2004-11-08 1:14 ` David Schwartz
2004-11-08 14:56 ` Pedro Venda (SYSADM)
2004-11-08 20:53 ` David Schwartz [this message]
2004-11-08 15:24 ` Alan Cox
2004-11-08 19:57 ` Geert Uytterhoeven
2004-11-08 21:33 ` Pedro Venda (SYSADM)
2004-11-08 21:54 ` David Schwartz
2004-11-08 23:25 ` Alan Cox
2004-11-08 20:53 ` GPL Violation of 'sveasoft' with GPL Linux Kernel/Busybox +code David Schwartz
2004-11-08 23:00 ` Alan Cox
2004-11-09 2:32 ` Dmitry Torokhov
2004-11-09 4:08 ` David Rees
2004-11-09 4:23 ` Dmitry Torokhov
2004-11-09 9:47 ` Alan Cox
2004-11-09 19:30 ` David Schwartz
2004-11-09 19:45 ` Chris Friesen
2004-11-09 20:23 ` David Schwartz
2004-11-09 20:48 ` Valdis.Kletnieks
2004-11-09 23:06 ` Alan Cox
2004-11-10 1:47 ` David Schwartz
2004-11-10 9:27 ` Geert Uytterhoeven
2004-11-10 18:14 ` Alan Cox
2004-11-10 19:32 ` Valdis.Kletnieks
2004-11-10 20:09 ` Stuart MacDonald
2004-11-10 21:18 ` Trever L. Adams
2004-11-09 23:22 ` Alan Cox
2004-11-10 1:34 ` Kyle Moffett
2004-11-10 2:01 ` Michael Poole
2004-11-10 3:02 ` Kyle Moffett
2004-11-10 4:14 ` Michael Poole
2004-11-10 4:28 ` Dmitry Torokhov
2004-11-10 21:11 ` Bill Davidsen
2004-11-10 23:09 ` Kyle Moffett
2004-11-10 22:14 ` Alan Cox
2004-11-15 14:47 ` David Woodhouse
2004-11-10 23:26 ` Dmitry Torokhov
2004-11-10 5:07 ` David Schwartz
2004-11-10 1:47 ` David Schwartz
2004-11-12 17:04 ` Horst von Brand
2004-11-09 21:13 ` Stuart MacDonald
2004-11-09 2:23 ` GPL Violation of 'sveasoft' with GPL Linux Kernel/Busybox + code Paul Jakma
2004-11-10 10:21 ` David Woodhouse
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=MDEHLPKNGKAHNMBLJOLKGECMPKAA.davids@webmaster.com \
--to=davids@webmaster.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pjvenda@rnl.ist.utl.pt \
/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®