public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Ulrich Mueller <ulm@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Contributed ebuilds and copyright questions
Date: Tue, 25 Oct 2016 14:54:55 +0200	[thread overview]
Message-ID: <22543.22047.228622.808177@a1i15.kph.uni-mainz.de> (raw)
In-Reply-To: <CAGfcS_=geF_f9C13gXSQrw1iKEvumRd1za9boX1n8JC6vek95g@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1129 bytes --]

>>>>> On Tue, 25 Oct 2016, Rich Freeman wrote:

> If they were under a non-compatible license like the CDDL then it
> would depend on whether the authors have the right to dual-license
> it under the GPL, or whether Gentoo is willing to accept
> CDDL-licensed ebuilds into the repository. Part of the draft policy
> is that every Gentoo project/repository have a list of accepted
> licenses. Off the top of my head I can't think of any issues with
> allowing incompatible but similar copyleft licenses into the main
> tree.

Having different licenses for ebuilds in the main tree would be a
nightmare, IMHO. It would make exchange of code between different
ebuilds much harder, if not impossible. Think of global issues like
the multilib conversion where similar code is used in many places.

Also, calling eclass functions could be considered linking. It is not
entirely clear to me if e.g. a binpkg built with a CDDL licensed
ebuild calling GPL licensed eclasses would be distributable at all.

So can we be strict there, please? Contributed ebuilds should have our
standard copyright header, or they will be rejected.

Ulrich

[-- Attachment #2: Type: application/pgp-signature, Size: 490 bytes --]

  reply	other threads:[~2016-10-25 12:55 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-24 22:29 [gentoo-dev] Contributed ebuilds and copyright questions Matt Turner
2016-10-24 22:52 ` William L. Thomson Jr.
2016-10-24 23:03 ` Rich Freeman
2016-10-24 23:12   ` Matt Turner
2016-10-24 23:18     ` Rich Freeman
2016-10-24 23:31       ` Matt Turner
2016-10-24 23:43         ` Rich Freeman
2016-10-24 23:47           ` Matt Turner
2016-10-25  1:12             ` Rich Freeman
2016-10-25  4:48       ` Daniel Campbell
2016-10-25 10:37         ` Rich Freeman
2016-10-25 12:54           ` Ulrich Mueller [this message]
2016-10-25 13:17             ` Rich Freeman
2016-10-25 13:56               ` Alexis Ballier
2016-10-25 14:15                 ` Rich Freeman
2016-10-25 15:17                   ` Alexis Ballier
2016-10-25 16:18                     ` Rich Freeman
2016-10-25 15:53               ` Ulrich Mueller
2016-10-25 16:23                 ` Rich Freeman
2016-10-25 10:49   ` Paweł Hajdan, Jr.
2016-10-25 11:16     ` Rich Freeman
2016-10-27 10:27 ` Mart Raudsepp

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=22543.22047.228622.808177@a1i15.kph.uni-mainz.de \
    --to=ulm@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.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