public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Ulrich Müller" <ulm@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/devmanual:master commit in: general-concepts/licenses/
Date: Mon, 29 Apr 2024 18:36:38 +0000 (UTC)	[thread overview]
Message-ID: <1714415649.5788aaadff50c5f29290cf7aa5d32c3932cd7e1f.ulm@gentoo> (raw)

commit:     5788aaadff50c5f29290cf7aa5d32c3932cd7e1f
Author:     Ulrich Müller <ulm <AT> gentoo <DOT> org>
AuthorDate: Mon Apr 29 10:35:13 2024 +0000
Commit:     Ulrich Müller <ulm <AT> gentoo <DOT> org>
CommitDate: Mon Apr 29 18:34:09 2024 +0000
URL:        https://gitweb.gentoo.org/proj/devmanual.git/commit/?id=5788aaad

general-concepts/licenses: Licenses must be plain text

Historically we had some PDF files in the repository, but the last
of them was removed in 2011.

Signed-off-by: Ulrich Müller <ulm <AT> gentoo.org>

 general-concepts/licenses/text.xml | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/general-concepts/licenses/text.xml b/general-concepts/licenses/text.xml
index 182cfb6..939b429 100644
--- a/general-concepts/licenses/text.xml
+++ b/general-concepts/licenses/text.xml
@@ -230,11 +230,11 @@ indicates <c>GPL-2+</c> license:
 <body>
 
 <p>
-If your package's license is not already in the tree, you must add the
-license before committing the package. When adding the license, use a
-plain text file (UTF-8 encoded) if at all possible. Some licenses are
-PDF files rather than plain text <d/> this should only be done if we
-are legally required to do so.
+If your package's license is not already in the tree, you must add the license
+before committing the package. When adding the license, use a plain text file
+(UTF-8 encoded), because non-text files
+<uri link="::general-concepts/tree/#What Belongs in the Tree?">do not belong
+in the repository</uri>.
 Finally you need to check if your license should be added to a license group
 as listed in the repository's <c>profiles/license_groups</c> file. For more
 information see


             reply	other threads:[~2024-04-29 18:36 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-29 18:36 Ulrich Müller [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-11-25 13:32 [gentoo-commits] proj/devmanual:master commit in: general-concepts/licenses/ 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-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=1714415649.5788aaadff50c5f29290cf7aa5d32c3932cd7e1f.ulm@gentoo \
    --to=ulm@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