Linux PPP protocol development
 help / color / mirror / Atom feed
From: Bill Unruh <unruh@physics.ubc.ca>
To: linux-ppp@vger.kernel.org
Subject: Re: pppd and plugin license
Date: Tue, 11 Oct 2016 16:35:42 +0000	[thread overview]
Message-ID: <alpine.LMD.2.03.1610110932090.17805@physics.ubc.ca> (raw)
In-Reply-To: <2c8a99fe282448d4b8c07b347fde7d78@svr-ies-mbx-01.mgc.mentorg.com>

For two licenses, the restrictions of both apply. For GPL, if the other
license restricts anything that GPL allows, then GPL does not give you a
license. Thus you have to see if there is anything in the BSD license which
restricts what the GPL grants. Also you need to check which GPL license (2 3
Library,...)

If you have real question about the law, a lawyer is the best source of
advice (one that is competent in Copyright and licensing law).


William G. Unruh __| Canadian Institute for|____ Tel: +1(604)822-3273
Physics&Astronomy _|___ Advanced Research _|____ Fax: +1(604)822-5324
UBC, Vancouver,BC _|_ Program in Cosmology |____ unruh@physics.ubc.ca
Canada V6T 1Z1 ____|____ and Gravity ______|_ www.theory.physics.ubc.ca/

On Tue, 11 Oct 2016, Waller, Claus wrote:

> Hello,
>
> I have a question about the pppd and the plugin licenses.
>
> As I can see the pppd has as license the old style BSD 4 Clause license and some of the plugins which are loaded as a dynamic library are GPL licensed.
> So my question is: Is it true that these licenses are incompatible to each other in the context of the pppd + a loaded plugin?

      parent reply	other threads:[~2016-10-11 16:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-11 13:32 pppd and plugin license Waller, Claus
2016-10-11 14:38 ` James Carlson
2016-10-11 16:35 ` Bill Unruh [this message]

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=alpine.LMD.2.03.1610110932090.17805@physics.ubc.ca \
    --to=unruh@physics.ubc.ca \
    --cc=linux-ppp@vger.kernel.org \
    /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