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: ebuild-maintenance/new-ebuild/
Date: Wed,  7 Apr 2021 17:35:28 +0000 (UTC)	[thread overview]
Message-ID: <1617816497.00f6bdcb2aed298e3d9c13b925811d1d35e39188.ulm@gentoo> (raw)

commit:     00f6bdcb2aed298e3d9c13b925811d1d35e39188
Author:     Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Sun Mar 21 04:43:18 2021 +0000
Commit:     Ulrich Müller <ulm <AT> gentoo <DOT> org>
CommitDate: Wed Apr  7 17:28:17 2021 +0000
URL:        https://gitweb.gentoo.org/proj/devmanual.git/commit/?id=00f6bdcb

ebuild-maintenance/new-ebuild: mention non-developers and large patches

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

 ebuild-maintenance/new-ebuild/text.xml | 12 +++++++++---
 1 file changed, 9 insertions(+), 3 deletions(-)

diff --git a/ebuild-maintenance/new-ebuild/text.xml b/ebuild-maintenance/new-ebuild/text.xml
index d8608be..7ef8254 100644
--- a/ebuild-maintenance/new-ebuild/text.xml
+++ b/ebuild-maintenance/new-ebuild/text.xml
@@ -24,9 +24,15 @@ The Gentoo repository should only be used for storing <c>.ebuild</c> files,
 as well as any small companion files, such as patches or sample configuration
 files. These files should have a size of at most 20 KiB and must be placed
 in the <c>mycat/mypkg/files</c> directory, which can be referenced as
-<c>${FILESDIR}</c> from within ebuilds. Larger patch files should be placed
-in your developer space on <c>dev.gentoo.org</c> instead, in order to minimize
-the repository size.
+<c>${FILESDIR}</c> from within ebuilds.
+</p>
+
+<p>
+Larger patches should be placed in your developer space on <c>dev.gentoo.org</c>
+instead of the tree, in order to minimize the repository size.
+Non-developers such as proxied maintainers can host patches at some stable
+location of their own <d/> there is no security issue here as the Manifest
+will record patch checksums at the time of commit.
 </p>
 
 <p>


             reply	other threads:[~2021-04-07 17:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-07 17:35 Ulrich Müller [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-10-21 11:46 [gentoo-commits] proj/devmanual:master commit in: ebuild-maintenance/new-ebuild/ Ulrich Müller
2022-01-22 23:40 Sam James
2021-03-30 16:10 Ulrich Müller
2020-03-02 10:49 Ulrich Müller

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=1617816497.00f6bdcb2aed298e3d9c13b925811d1d35e39188.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