From: Jim Choate <ravage@einstein.ssz.com>
To: <9fans@cse.psu.edu>
Cc: <hangar18-general@open-forge.com>
Subject: Re: [9fans] Plan9 licence clarification
Date: Mon, 23 Feb 2004 09:24:47 -0600 [thread overview]
Message-ID: <Pine.LNX.4.33.0402230921400.28584-100000@einstein.ssz.com> (raw)
In-Reply-To: <4a16953fbf9c2b343f2014b9264ed5d2@plan9.bell-labs.com>
On Sun, 22 Feb 2004, David Presotto wrote:
> The intention is that linking with our libraries not be considered
> contributing or redistributing, i.e., you can distribute without
> that being considered part of 'the original program'.
>
> However, if you include the source of the libraries (or any other
> part of the system) that is protected by the license constraints.
And there is no requirement to provide source if you include the binaries.
So, I can build a project and link it into P9 and as long as no P9 source
goes with it I'm ok? The license (Open or Closed) with regard to the
project is not relevant. Only whether I provide P9 source.
If I do include any source from P9 then I must provide souce to the
product/program/extension.
Correct?
-- --
Open Forge, LLC 24/365 Onsite Support for PCs, Networks, & Game Consoles
512-695-4126 (Austin, Tx.) help@open-forge.com
Hangar 18 Open Source Distributed Computing Using Plan 9 & Linux
512-451-7087 http://open-forge.org/hangar18
James Choate 512-451-7087 ravage@ssz.com jchoate@open-forge.com
next prev parent reply other threads:[~2004-02-23 15:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-22 13:49 David Presotto
2004-02-23 15:24 ` Jim Choate [this message]
2004-02-23 15:52 ` David Presotto
2004-02-23 16:18 ` Jim Choate
2004-02-25 7:10 ` Einar Karttunen
2004-02-25 13:49 ` David Presotto
2004-02-27 18:14 ` [9fans] Hangar 18 Update - March 2004 Jim Choate
-- strict thread matches above, loose matches on Subject: below --
2004-02-22 9:12 [9fans] Plan9 licence clarification Einar Karttunen
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=Pine.LNX.4.33.0402230921400.28584-100000@einstein.ssz.com \
--to=ravage@einstein.ssz.com \
--cc=9fans@cse.psu.edu \
--cc=hangar18-general@open-forge.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;
as well as URLs for NNTP newsgroup(s).