Gentoo Archives: gentoo-commits

From: "Ulrich Müller" <ulm@g.o>
To: gentoo-commits@l.g.o
Subject: [gentoo-commits] proj/devmanual:master commit in: eclass-writing/
Date: Tue, 30 Mar 2021 06:55:52
Message-Id: 1617087203.97c28330bb6906f046337c4000e69ef52c52296f.ulm@gentoo
1 commit: 97c28330bb6906f046337c4000e69ef52c52296f
2 Author: Sam James <sam <AT> gentoo <DOT> org>
3 AuthorDate: Mon Mar 22 05:37:37 2021 +0000
4 Commit: Ulrich Müller <ulm <AT> gentoo <DOT> org>
5 CommitDate: Tue Mar 30 06:53:23 2021 +0000
6 URL: https://gitweb.gentoo.org/proj/devmanual.git/commit/?id=97c28330
7
8 eclass-writing: mention etiquette with respect to metadata invalidation
9
10 Signed-off-by: Sam James <sam <AT> gentoo.org>
11 Signed-off-by: Ulrich Müller <ulm <AT> gentoo.org>
12
13 eclass-writing/text.xml | 11 +++++++++++
14 1 file changed, 11 insertions(+)
15
16 diff --git a/eclass-writing/text.xml b/eclass-writing/text.xml
17 index adf3671..ccebfb6 100644
18 --- a/eclass-writing/text.xml
19 +++ b/eclass-writing/text.xml
20 @@ -90,6 +90,17 @@ Committing a broken eclass can kill huge numbers of packages. Since
21 A simple way to verify syntax is <c>bash -n foo.eclass</c>.
22 </p>
23
24 +<note>
25 +Given that updating an eclass will invalidate the cache of all consumer ebuilds,
26 +it is good etiquette to ping other developers in e.g. <c>#gentoo-dev</c>
27 +on IRC or informally determine if there are other similar changes (mainly
28 +documentation) which should be pushed at the same time in order to avoid
29 +unnecessary cache regeneration within a few hours or days of each other.
30 +
31 +The same applies to your own work <d/> please prepare all of your commits and
32 +batch push them at once where possible.
33 +</note>
34 +
35 </body>
36 </section>