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>
