-
Notifications
You must be signed in to change notification settings - Fork 54
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
sys-kernel/genkernel-next deprecation #22
Comments
If Best, sakaki |
Yes, for now creating e.g.
should work. I'll add this to the guide now as a band-aid until this is resolved one way or other upstream. |
Guide updated. |
so far sabayon is preparing to sawp base to funtoo. as funtoo has a more backdated but stable toolbase , and the option of newer tools. |
Now that |
I am using a recent kernel (5.8+) because of hardware issues. With these recent kernel versions + genkernel-next-69 the kernel does not boot. With genkernel-next-70 booting the recent kernels worked again, buildkernel worked fine, too. |
I am currently installing fresh Gentoo using the guide. Just adding I had to add ln -s /var/cache/distfiles/busybox-1.32.0.tar.bz2 /var/lib/genkernel/src/ |
31 Oct 2020: sadly, due to legal obligations arising from a recent change in my 'real world' job, I must announce I am standing down as maintainer of this project with immediate effect. For the meantime, I will leave the repo up (for historical interest, and since the ebuilds etc. may be of use to others); however, I plan no further updates, nor will I be accepting / actioning further pull requests or bug reports from this point. Email requests for support will also have to be politely declined, so, please treat this as an effective EOL notice. |
The current genkernel-next package is being deprecated in the official Gentoo portage tree:
https://bugs.gentoo.org/719968
sakaki-tools:sys-kernel/buildkernel depends on sys-kernel/genkernel-next as a runtime dependency:
Are there plans to support the Gentoo-supplied sys-kernel/genkernel?
The text was updated successfully, but these errors were encountered: