unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: <tomas@tuxteam.de>
To: Arthur Miller <arthur.miller.no1@gmail.com>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Is BSD licence compatible to export with emacs modules?
Date: Thu, 27 Jul 2017 23:20:13 +0200	[thread overview]
Message-ID: <20170727212013.GD28402@tuxteam.de> (raw)
In-Reply-To: <CAHk_L7ow77X7AeHA=hjv_7TxnUSM1dT9QetDT4_xWsPVV1rqtg@mail.gmail.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Thu, Jul 27, 2017 at 05:26:51PM +0200, Arthur Miller wrote:
> Just a short question: if I wrap a bsd-licensed code into n emacs module,
> is it compatible
> with GPL license? Is it OK to export with
> 
> int plugin_is_GPL_compatible;
> 
> Does that symbol aim at my own written module code, or does it even include
> 
> used 3rd party code (which in this case is licenced under the BSD licence)?

Yes. BSD is GPL compatible [1]. ( assume it's the currently common "modified"
or "three-clause" license [2] and not the original, four-clause license [4],
which is pretty uncommon these days. The four-clause license has this non-
advertising clause.

Cheers

[1] https://www.gnu.org/licenses/license-list#GPLCompatibleLicenses
[2] https://directory.fsf.org/wiki/License:BSD_3Clause
[3] https://directory.fsf.org/wiki/License:BSD_4Clause

- -- tomás
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEARECAAYFAll6WQ0ACgkQBcgs9XrR2kYQNgCfdZLuqzrw7xvx7Tx5R3AkJmIF
xzAAnApo+y4iBrBlZn1KHGcM4deuAiYX
=WROV
-----END PGP SIGNATURE-----



  reply	other threads:[~2017-07-27 21:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-27 15:26 Is BSD licence compatible to export with emacs modules? Arthur Miller
2017-07-27 21:20 ` tomas [this message]
2017-07-27 21:37   ` Emanuel Berg
2017-07-28  8:32     ` tomas

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20170727212013.GD28402@tuxteam.de \
    --to=tomas@tuxteam.de \
    --cc=arthur.miller.no1@gmail.com \
    --cc=help-gnu-emacs@gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).