diff options
author | 2021-03-22 05:30:00 +0000 | |
---|---|---|
committer | 2021-03-30 08:53:23 +0200 | |
commit | 1916f42b99447c45e1f8e920dcdd025715a7c328 (patch) | |
tree | 5118b1ff0b5102c96f1f12067842666519db1f79 /eclass-writing | |
parent | ebuild-writing/common-mistakes: extend 'DEPEND is incomplete' (diff) | |
download | devmanual-1916f42b99447c45e1f8e920dcdd025715a7c328.tar.gz devmanual-1916f42b99447c45e1f8e920dcdd025715a7c328.tar.bz2 devmanual-1916f42b99447c45e1f8e920dcdd025715a7c328.zip |
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@gentoo.org>
Signed-off-by: Ulrich Müller <ulm@gentoo.org>
Diffstat (limited to 'eclass-writing')
-rw-r--r-- | eclass-writing/text.xml | 5 |
1 files changed, 4 insertions, 1 deletions
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> |