[gentoo-commits] proj/devmanual:master commit in: ebuild-maintenance/new-ebuild/
commit: fd399e73274e120f5171d2f75fe0dfbe8c032b1d Author: Ulrich Müller gentoo org> AuthorDate: Sat Oct 21 11:43:54 2023 + Commit: Ulrich Müller gentoo org> CommitDate: Sat Oct 21 11:43:54 2023 + URL:https://gitweb.gentoo.org/proj/devmanual.git/commit/?id=fd399e73 ebuild-maintenance/new-ebuild; Fix link to bugzilla advanced search Also update the paragraph explaining it. Signed-off-by: Ulrich Müller gentoo.org> ebuild-maintenance/new-ebuild/text.xml | 19 ++- 1 file changed, 10 insertions(+), 9 deletions(-) diff --git a/ebuild-maintenance/new-ebuild/text.xml b/ebuild-maintenance/new-ebuild/text.xml index ea6dcab..10793e0 100644 --- a/ebuild-maintenance/new-ebuild/text.xml +++ b/ebuild-maintenance/new-ebuild/text.xml @@ -8,15 +8,16 @@ -Before writing a new ebuild, check -https://bugs.gentoo.org/;>bugs.gentoo.org -to see if an ebuild has already been written for the package, but has not yet -been added to the Gentoo repository. Go to https://bugs.gentoo.org/;>bugs.gentoo.org, choose query and select -Advanced Search; as product select Gentoo Linux, as component select -ebuilds. In the search field put the name of the ebuild and as status -select all possible fields, then submit the query. For you lazy people, click -https://bugs.gentoo.org/query.cgi?format=advancedproduct=Gentoo%20Linuxcomponent=New%20Ebuildsbug_Status=UNCONFIRMEDbug_status=CONFIRMEDbug_status=IN_PROGRESSbug_status=RESOLVEDbug_status=VERIFIED;>here. +Before writing a new ebuild, check https://bugs.gentoo.org/;> +bugs.gentoo.org to see if an ebuild has already been written for +the package, but has not yet been added to the Gentoo repository. Go to +https://bugs.gentoo.org/;>bugs.gentoo.org, choose query and +select Advanced Search; as product select Gentoo Linux, as component +select New packages. In the search field put the name of the ebuild and +as status and resolution select all possible fields, then submit the query. +For you lazy people, here is a +https://bugs.gentoo.org/query.cgi?format=advancedproduct=Gentoo%20Linuxcomponent=New%20packages;> +Bugzilla advanced search link.
[gentoo-commits] proj/devmanual:master commit in: ebuild-maintenance/new-ebuild/
commit: e7c201902967728dffa91c9cca11c5896e15c98c Author: Sam James gentoo org> AuthorDate: Sat Jan 22 23:39:42 2022 + Commit: Sam James gentoo org> CommitDate: Sat Jan 22 23:40:54 2022 + URL:https://gitweb.gentoo.org/proj/devmanual.git/commit/?id=e7c20190 ebuild-maintenance/new-ebuild: use .patch, not .diff We almost always use .patch now, so let's just reference it here too. Signed-off-by: Sam James gentoo.org> ebuild-maintenance/new-ebuild/text.xml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/ebuild-maintenance/new-ebuild/text.xml b/ebuild-maintenance/new-ebuild/text.xml index 7ef8254..eebdb8d 100644 --- a/ebuild-maintenance/new-ebuild/text.xml +++ b/ebuild-maintenance/new-ebuild/text.xml @@ -101,8 +101,8 @@ this directory; any files bigger than 20KB-or-so should go to the mirrors to lower the amount of (unneeded) files our users have to download. You may want to consider naming patches you create yourself just to get your package to build with a version-specific name, such -as mypkg-1.0-gentoo.diff, or more -simply, 1.0-gentoo.diff. Also note that the +as mypkg-1.0-gentoo.patch, or more +simply, 1.0-gentoo.patch. Also note that the gentoo extension informs people that this patch was created by us, the Gentoo Linux developers, rather than having been grabbed from a mailing list or somewhere else. Again, you should not compress these
[gentoo-commits] proj/devmanual:master commit in: ebuild-maintenance/new-ebuild/
commit: 00f6bdcb2aed298e3d9c13b925811d1d35e39188
Author: Sam James gentoo org>
AuthorDate: Sun Mar 21 04:43:18 2021 +
Commit: Ulrich Müller gentoo org>
CommitDate: Wed Apr 7 17:28:17 2021 +
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 gentoo.org>
Signed-off-by: Ulrich Müller 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
.ebuild 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 mycat/mypkg/files directory, which can be referenced as
-${FILESDIR} from within ebuilds. Larger patch files should be placed
-in your developer space on dev.gentoo.org instead, in order to minimize
-the repository size.
+${FILESDIR} from within ebuilds.
+
+
+
+Larger patches should be placed in your developer space on
dev.gentoo.org
+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 there is no security issue here as the Manifest
+will record patch checksums at the time of commit.
[gentoo-commits] proj/devmanual:master commit in: ebuild-maintenance/new-ebuild/
commit: be07d60d328e03200d4864be66782123aad756f1 Author: Sam James gentoo org> AuthorDate: Sun Mar 21 04:36:51 2021 + Commit: Ulrich Müller gentoo org> CommitDate: Tue Mar 30 16:00:54 2021 + URL:https://gitweb.gentoo.org/proj/devmanual.git/commit/?id=be07d60d ebuild-maintenance/new-ebuild: mention pkgdev as an alternative to repoman Signed-off-by: Sam James gentoo.org> Signed-off-by: Ulrich Müller gentoo.org> ebuild-maintenance/new-ebuild/text.xml | 7 --- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/ebuild-maintenance/new-ebuild/text.xml b/ebuild-maintenance/new-ebuild/text.xml index ad7f74c..d8608be 100644 --- a/ebuild-maintenance/new-ebuild/text.xml +++ b/ebuild-maintenance/new-ebuild/text.xml @@ -48,9 +48,10 @@ examples. -When committing to git, all developers should use repoman commit -instead of git commit to submit their ebuilds. Before committing, -please run repoman full to make sure you didn't forget something. +When committing to git, all developers should use repoman commit or +pkgdev commit with pkgdev push instead of git commit to +submit their ebuilds. Before committing, please run repoman full or +pkgcheck scan to make sure you didn't forget something.
[gentoo-commits] proj/devmanual:master commit in: ebuild-maintenance/new-ebuild/
commit: 5161bfd22b3d53941986b7c55ca7c3c06e54a470
Author: Ulrich Müller gentoo org>
AuthorDate: Mon Mar 2 10:46:32 2020 +
Commit: Ulrich Müller gentoo org>
CommitDate: Mon Mar 2 10:46:32 2020 +
URL:https://gitweb.gentoo.org/proj/devmanual.git/commit/?id=5161bfd2
ebuild-maintenance/new-ebuild: Update "What (not) to put in the tree".
Closes: https://bugs.gentoo.org/585218
Reported-by: Jonas Stein gentoo.org>
Signed-off-by: Ulrich Müller gentoo.org>
ebuild-maintenance/new-ebuild/text.xml | 27 +--
1 file changed, 13 insertions(+), 14 deletions(-)
diff --git a/ebuild-maintenance/new-ebuild/text.xml
b/ebuild-maintenance/new-ebuild/text.xml
index 332b527..ad7f74c 100644
--- a/ebuild-maintenance/new-ebuild/text.xml
+++ b/ebuild-maintenance/new-ebuild/text.xml
@@ -20,20 +20,19 @@ select all possible fields, then submit the query. For you
lazy people, click
-In general, the Gentoo repository should only be used for storing
-.ebuild files, as well as any relatively small companion
-files, such as patches or sample configuration files. These types of
-files should be placed in the mycat/mypkg/files directory
-to keep the main mycat/mypkg directory uncluttered.
-Exceptions to this rule are for larger patch files (we recommend this
-for patches above 20KB) which should be distributed as tarballs via the
-Gentoo
-mirror system so that people do not waste excessive amounts of
-bandwidth and hard drive space. Also, you should not add binary
-(non-ASCII) files to the git tree. Also, speaking of merging changes,
-any patches you add to Portage should generally not be
-compressed. This will allow git to merge changes and correctly inform
-developers of conflicts.
+The Gentoo repository should only be used for storing .ebuild 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 mycat/mypkg/files directory, which can be referenced as
+${FILESDIR} from within ebuilds. Larger patch files should be placed
+in your developer space on dev.gentoo.org instead, in order to minimize
+the repository size.
+
+
+
+The files in the repository should be uncompressed plain text files, i.e.,
+no binaries. This will allow the version control system to merge changes and
+correctly inform developers of conflicts.
