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:53
Message-Id: 1617087203.1916f42b99447c45e1f8e920dcdd025715a7c328.ulm@gentoo
1 commit: 1916f42b99447c45e1f8e920dcdd025715a7c328
2 Author: Sam James <sam <AT> gentoo <DOT> org>
3 AuthorDate: Mon Mar 22 05:30:00 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=1916f42b
7
8 eclass-writing: mention that checking (official) overlays may be useful
9
10 This is just a politeness/interesting thought which people may want to
11 consider, rather than a hard requirement.
12
13 For "official" overlays in particular, a Gentoo developer should be able
14 to give the responsible developer(s) a quick ping to ensure they're
15 aware if their overlay seems to be heavily using legacy functionality.
16
17 Signed-off-by: Sam James <sam <AT> gentoo.org>
18 Signed-off-by: Ulrich Müller <ulm <AT> gentoo.org>
19
20 eclass-writing/text.xml | 5 ++++-
21 1 file changed, 4 insertions(+), 1 deletion(-)
22
23 diff --git a/eclass-writing/text.xml b/eclass-writing/text.xml
24 index 70f9fff..adf3671 100644
25 --- a/eclass-writing/text.xml
26 +++ b/eclass-writing/text.xml
27 @@ -70,7 +70,10 @@ package, and thus does not typically require changes to be emailed for review.
28
29 <p>
30 When removing a function or changing the API of an eclass, make sure that
31 -it doesn't break any ebuilds in the Gentoo repository.
32 +it doesn't break any ebuilds in the Gentoo repository. Optionally, you may wish
33 +to do a survey of some (official) overlays like <c>::guru</c>, <c>::musl</c>, or
34 +<c>::science</c> in order to better understand how it is currently used and
35 +<d/> where possible <d/> avoid breakage by pinging the maintainers directly.
36 </p>
37
38 <p>