commit: f7c8ae62be6bca0ddba74a43d38e7e9fac893906
Author: Ionen Wolkens <ionen <AT> gentoo <DOT> org>
AuthorDate: Tue May 30 01:47:11 2023 +0000
Commit: Ionen Wolkens <ionen <AT> gentoo <DOT> org>
CommitDate: Tue May 30 02:34:59 2023 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=f7c8ae62
linux-mod-r1.eclass: mention dist-kernel for upper bounds
The virtual allows pulling older slots without being downgraded,
which may make things confusing for USE=dist-kernel automatic
rebuilds.
If try to downgrade the virtual, it will suggest downgrading
the kernel too and likely won't need to explain further.
Beside that, rather stay somewhat vague there. This is not
downgrade instructions.
(note will take the liberty to do quick edits without ML
review for the time being, very few consumers at the moment)
Signed-off-by: Ionen Wolkens <ionen <AT> gentoo.org>
eclass/linux-mod-r1.eclass | 8 +++++++-
1 file changed, 7 insertions(+), 1 deletion(-)
diff --git a/eclass/linux-mod-r1.eclass b/eclass/linux-mod-r1.eclass
index 595711008627..73e7e7f8ff0b 100644
--- a/eclass/linux-mod-r1.eclass
+++ b/eclass/linux-mod-r1.eclass
@@ -1058,7 +1058,13 @@ _modules_sanity_kernelversion() {
ewarn "with the current kernel (${KV_FULL}), it was
either hardly"
ewarn "tested or is known broken. It is recommended to
use one of:"
ewarn
- ewarn " <=sys-kernel/gentoo-kernel-${max}"
+ # fwiw we do not know what is *actually* used or wanted
even with
+ # the USE, so stay a bit vague and always mention both
dist+sources
+ if use dist-kernel; then
+ ewarn " <=virtual/dist-kernel-${max} or"
+ else
+ ewarn " <=sys-kernel/gentoo-kernel-${max} or"
+ fi
ewarn " <=sys-kernel/gentoo-sources-${max}"
ewarn
ewarn "or equivalent rather than file downstream bug
reports if run into"
