commit: 09db1c5df37cfab3f01aaf701a4fbdfc1af46c55 Author: Sam James <sam <AT> gentoo <DOT> org> AuthorDate: Sat Feb 28 13:52:36 2026 +0000 Commit: Sam James <sam <AT> gentoo <DOT> org> CommitDate: Sat Feb 28 19:06:53 2026 +0000 URL: https://gitweb.gentoo.org/proj/devmanual.git/commit/?id=09db1c5d
general-concepts/slotting: mention incompatible changes, informing users app-containers/docker-compose is perhaps a good example of this. Bug: https://bugs.gentoo.org/835431 Signed-off-by: Sam James <sam <AT> gentoo.org> general-concepts/slotting/text.xml | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/general-concepts/slotting/text.xml b/general-concepts/slotting/text.xml index 767238a..2b0be0b 100644 --- a/general-concepts/slotting/text.xml +++ b/general-concepts/slotting/text.xml @@ -159,6 +159,16 @@ of user scripts or tools, and build systems which expect the generic name to be available. </p> +<p> +New slots are usually incompatible with older versions in some regard like +UI, syntax, behaviour. A new version of a slotted executable could suddenly +break users' workflows, so a +<uri link="::general-concepts/news/">news item</uri> +or +<uri link="::ebuild-writing/messages/">ewarn</uri> +may be appropriate. +</p> + <p> An <c>eselect</c> module is often made available for these cases, though ebuilds normally shouldn't depend on its use.
