commit: 97c28330bb6906f046337c4000e69ef52c52296f Author: Sam James <sam <AT> gentoo <DOT> org> AuthorDate: Mon Mar 22 05:37:37 2021 +0000 Commit: Ulrich Müller <ulm <AT> gentoo <DOT> org> CommitDate: Tue Mar 30 06:53:23 2021 +0000 URL: https://gitweb.gentoo.org/proj/devmanual.git/commit/?id=97c28330
eclass-writing: mention etiquette with respect to metadata invalidation Signed-off-by: Sam James <sam <AT> gentoo.org> Signed-off-by: Ulrich Müller <ulm <AT> gentoo.org> eclass-writing/text.xml | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/eclass-writing/text.xml b/eclass-writing/text.xml index adf3671..ccebfb6 100644 --- a/eclass-writing/text.xml +++ b/eclass-writing/text.xml @@ -90,6 +90,17 @@ Committing a broken eclass can kill huge numbers of packages. Since A simple way to verify syntax is <c>bash -n foo.eclass</c>. </p> +<note> +Given that updating an eclass will invalidate the cache of all consumer ebuilds, +it is good etiquette to ping other developers in e.g. <c>#gentoo-dev</c> +on IRC or informally determine if there are other similar changes (mainly +documentation) which should be pushed at the same time in order to avoid +unnecessary cache regeneration within a few hours or days of each other. + +The same applies to your own work <d/> please prepare all of your commits and +batch push them at once where possible. +</note> + </body> </section>
