[gentoo-commits] proj/devmanual:master commit in: eclass-writing/

["Ulrich Müller" <ulm@gentoo.org>]

commit:     1916f42b99447c45e1f8e920dcdd025715a7c328
Author:     Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Mon Mar 22 05:30:00 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=1916f42b

eclass-writing: mention that checking (official) overlays may be useful

This is just a politeness/interesting thought which people may want to
consider, rather than a hard requirement.

For "official" overlays in particular, a Gentoo developer should be able
to give the responsible developer(s) a quick ping to ensure they're
aware if their overlay seems to be heavily using legacy functionality.

Signed-off-by: Sam James <sam <AT> gentoo.org>
Signed-off-by: Ulrich Müller <ulm <AT> gentoo.org>

 eclass-writing/text.xml | 5 ++++-
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/eclass-writing/text.xml b/eclass-writing/text.xml
index 70f9fff..adf3671 100644
--- a/eclass-writing/text.xml
+++ b/eclass-writing/text.xml
@@ -70,7 +70,10 @@ package, and thus does not typically require changes to be emailed for review.
 
 <p>
 When removing a function or changing the API of an eclass, make sure that
-it doesn't break any ebuilds in the Gentoo repository.
+it doesn't break any ebuilds in the Gentoo repository. Optionally, you may wish
+to do a survey of some (official) overlays like <c>::guru</c>, <c>::musl</c>, or
+<c>::science</c> in order to better understand how it is currently used and
+<d/> where possible <d/> avoid breakage by pinging the maintainers directly.
 </p>
 
 <p>