public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Jonas Stein <jstein@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Should we allow "GPL, v2 or later" for ebuilds?
Date: Mon, 27 Jan 2020 13:15:26 +0100	[thread overview]
Message-ID: <0528f7e6-3416-0f1c-c276-f018576ef371@gentoo.org> (raw)
In-Reply-To: <w6g4kwhf7o9.fsf@kph.uni-mainz.de>


[-- Attachment #1.1: Type: text/plain, Size: 575 bytes --]

> Note that we could easily revert from GPL-2+ to GPL-2 if it would turn
> out to be too much trouble.
> 
> Thoughts?

I would prefer a single license for all ebuilds.
GPL-2+ or GPL-2 or GPL-... does not matter to me, I am willing to sign,
that all my contributions may be licensed also as GPL-...

IANAL, but I would expect that the license does not change anything for
trivial ebuilds.
The level of creativity ("Schöpfungshöhe") is not high enough for most
ebuilds.
Most ebuild contain only an obvious recipe to install the software.

-- 
Best,
Jonas


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 636 bytes --]

  parent reply	other threads:[~2020-01-27 12:16 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-27 11:41 [gentoo-dev] Should we allow "GPL, v2 or later" for ebuilds? Ulrich Mueller
2020-01-27 11:52 ` Michał Górny
2020-01-27 12:15 ` Jonas Stein [this message]
2020-01-27 15:31 ` Rich Freeman
2020-01-30 11:20 ` Haelwenn (lanodan) Monnier
2020-01-30 13:19   ` Rich Freeman
2020-02-04  0:42     ` Kent Fredric
2020-02-11 15:05     ` Haelwenn (lanodan) Monnier
2020-02-11 15:52       ` Rich Freeman
2020-02-12  4:37         ` Haelwenn (lanodan) Monnier
2020-01-30 13:39 ` Hanno Böck
2020-01-30 14:23   ` Rich Freeman

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=0528f7e6-3416-0f1c-c276-f018576ef371@gentoo.org \
    --to=jstein@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