public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Göktürk Yüksek" <gokturk@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/devmanual:master commit in: general-concepts/licenses/
Date: Wed, 16 Oct 2019 18:49:56 +0000 (UTC)	[thread overview]
Message-ID: <1571251716.6e513443da0103b0c849449af124e1cd7173f412.gokturk@gentoo> (raw)

commit:     6e513443da0103b0c849449af124e1cd7173f412
Author:     Michał Górny <mgorny <AT> gentoo <DOT> org>
AuthorDate: Sun Sep  8 17:43:56 2019 +0000
Commit:     Göktürk Yüksek <gokturk <AT> gentoo <DOT> org>
CommitDate: Wed Oct 16 18:48:36 2019 +0000
URL:        https://gitweb.gentoo.org/proj/devmanual.git/commit/?id=6e513443

general-concepts/licenses: all-rights-reserved default, restricts

Add a paragraph on applicable restrictions per license terms.  Also
clearly indicate that sources with no license are all-rights-reserved.

Acked-by: Michael Orlitzky <mjo <AT> gentoo.org>
Signed-off-by: Michał Górny <mgorny <AT> gentoo.org>
Signed-off-by: Göktürk Yüksek <gokturk <AT> gentoo.org>

 general-concepts/licenses/text.xml | 22 +++++++++++++++++++---
 1 file changed, 19 insertions(+), 3 deletions(-)

diff --git a/general-concepts/licenses/text.xml b/general-concepts/licenses/text.xml
index 86ffc8d..f7e904e 100644
--- a/general-concepts/licenses/text.xml
+++ b/general-concepts/licenses/text.xml
@@ -25,9 +25,7 @@ LICENSE="LGPL-2.1+ tools? ( GPL-2+ )"
 If the package sources include additional files that are not installed,
 their license should not be listed. However, if those files are used
 at build time, then the license must not impose any restrictions that
-could prevent users from building the software. Please also note
-that some licenses may impose additional restrictons, e.g. fetch
-and/or mirroring restriction.
+could prevent users from building the software.
 </p>
 
 <p>
@@ -39,6 +37,16 @@ be used) then use the following syntax:
 LICENSE="|| ( foo bar )"
 </codesample>
 
+<p>
+If the license of a package does not explicitly permit redistributing
+distfiles found in <c>SRC_URI</c>, the corresponding ebuilds must have
+<c>RESTRICT=mirror</c>. If the license does not permit distributing
+Gentoo binary packages built from the source, the ebuilds should have
+<c>RESTRICT=bindist</c>. Some EULAs may also require the user to fetch
+distfiles manually, in which case <c>RESTRICT=fetch</c> is necessary.
+Note that <c>RESTRICT=fetch</c> implies <c>RESTRICT=mirror</c>.
+</p>
+
 <section>
 <title>Determining the correct license</title>
 <body>
@@ -81,6 +89,14 @@ of applicable licenses but the exact application of licenses and their
 versions are specified elsewhere.
 </p>
 
+<p>
+If the package does not indicate any license, then you should contact
+the author for clarification. Adding packages with no explicit license
+statement is strongly discouraged. If they are present already, they
+ought to have <c>all-rights-reserved</c> license,
+and <c>RESTRICT="bindist mirror"</c>.
+</p>
+
 <p>
 Please watch for license conflicts. If the license indicated
 by the package is incompatible with the licenses used by its sources


             reply	other threads:[~2019-10-16 18:50 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-16 18:49 Göktürk Yüksek [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-04-29 18:36 [gentoo-commits] proj/devmanual:master commit in: general-concepts/licenses/ Ulrich Müller
2023-11-25 13:32 Ulrich Müller
2021-02-13  9:40 Ulrich Müller
2020-05-06 14:29 Ulrich Müller
2020-05-06 14:29 Ulrich Müller
2020-01-14  8:42 Ulrich Müller
2019-12-26 23:53 Göktürk Yüksek
2019-10-16 18:49 Göktürk Yüksek
2019-09-08 17:55 Ulrich Müller
2018-12-20  4:56 Göktürk Yüksek
2018-12-20  4:56 Göktürk Yüksek
2018-12-20  4:56 Göktürk Yüksek
2018-12-20  4:56 Göktürk Yüksek
2018-12-20  4:56 Göktürk Yüksek
2012-10-27 17:48 Markos Chandras
2012-10-27 17:44 Markos Chandras
2012-10-27 17:44 Markos Chandras
2012-10-12 17:44 Ulrich Mueller

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=1571251716.6e513443da0103b0c849449af124e1cd7173f412.gokturk@gentoo \
    --to=gokturk@gentoo.org \
    --cc=gentoo-commits@lists.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