From owner-freebsd-chat Mon Feb 22 19:58:13 1999 Delivered-To: freebsd-chat@freebsd.org Received: from lariat.lariat.org (lariat.lariat.org [206.100.185.2]) by hub.freebsd.org (Postfix) with ESMTP id 7A80C11001 for ; Mon, 22 Feb 1999 19:58:10 -0800 (PST) (envelope-from brett@lariat.org) Received: (from brett@localhost) by lariat.lariat.org (8.8.8/8.8.6) id UAA00442; Mon, 22 Feb 1999 20:58:04 -0700 (MST) Message-Id: <4.1.19990222202747.00978280@mail.lariat.org> X-Sender: brett@mail.lariat.org X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Mon, 22 Feb 1999 20:55:44 -0700 To: Terry Lambert From: Brett Glass Subject: Re: GPL issues (Was: More important Windows Refund Day Cc: tlambert@primenet.com, chat@FreeBSD.ORG In-Reply-To: <199902230323.UAA15544@usr08.primenet.com> References: <4.1.19990222201531.03fc77d0@mail.lariat.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-chat@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org At 03:23 AM 2/23/99 +0000, Terry Lambert wrote: >I think you have misread the license: > >3.7. Larger Works. > You may create a Larger Work by combining Covered Code with > other code not governed by the terms of this License and > distribute the Larger Work as a single product. In such a > case, You must make sure the requirements of this License > are fulfilled for the Covered Code. What I saw was: | 1.9. "Modifications" means any addition to or deletion from the substance | or structure of either the Original Code or any previous Modifications. When | Covered Code is released as a series of files, a Modification is: | | A.Any addition to or deletion from the contents of a file containing | Original Code or previous Modifications. | | B.Any new file that contains any part of the Original Code or previous | Modifications. And then.... | 3.2. Availability of Source Code. Any Modification which You create or to which You contribute must be made | available in Source Code form under the terms of this License This is a little snaky. If the definition of "file" includes the binary file from which you burn your ROMS, you're toast. Ditto if device drivers that are statically linked (and eCos doesn't seem to have dynamic device driver loading) must have source code published. So, I'm not sure how safe one is. It might turn out to be more benign than the GPL, but I'd ask a lawyer before assuming I wouldn't get bit. --Brett To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-chat" in the body of the message