From: David Presotto <presotto@closedmind.org>
To: ekarttun@cs.helsinki.fi, 9fans@cse.psu.edu
Subject: Re: [9fans] Plan9 licence clarification
Date: Sun, 22 Feb 2004 08:49:51 -0500 [thread overview]
Message-ID: <4a16953fbf9c2b343f2014b9264ed5d2@plan9.bell-labs.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 323 bytes --]
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.
[-- Attachment #2: Type: message/rfc822, Size: 2682 bytes --]
From: Einar Karttunen <ekarttun@cs.helsinki.fi>
To: Plan9 ML <9fans@cse.psu.edu>
Subject: [9fans] Plan9 licence clarification
Date: Sun, 22 Feb 2004 11:12:06 +0200
Message-ID: <20040222091206.GA20532@melkki.cs.Helsinki.FI>
Hello
Does the Plan9 licence ("Lucent Public Licence 1.02") imply any
licensing constraints for code linking against code protected by it?
That is, can I link against the plan9 code if my code is under a
different (BSD) licence? The licence speaks of "the original program"
but that sounds quite ambiguous in the case of libraries...
- Einar Karttunen
next reply other threads:[~2004-02-22 13:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-22 13:49 David Presotto [this message]
2004-02-23 15:24 ` Jim Choate
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=4a16953fbf9c2b343f2014b9264ed5d2@plan9.bell-labs.com \
--to=presotto@closedmind.org \
--cc=9fans@cse.psu.edu \
--cc=ekarttun@cs.helsinki.fi \
/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).