includes latest patchset, but some important changes to ebuild. 1) have to exclude patches 2400, 25*, 26*, and 27*, since the ck patchset won't apply. 2) removed redundant call to detect-version.
Created attachment 88712 [details] ck-sources-2.6.16_p12.ebuild
With revisions posted in bug #136076, all but three genpatches can be applied. 2500, 2505, and 2605 fail. The revised ebuild required changes to kernel-2.eclass to function as expected. Otherwise, ck patch will not apply at all. New patch introduces the use of UNIPATCH_GENPATCHES_LAST flag and alters the exclude list to specifically mask the patches that won't apply.
Created attachment 88830 [details] ck-sources-2.6.16_p12.ebuild this ebuild will not work with current kernel-2.eclass. It is intended for the kernel-2.eclass I patched only.
Created attachment 88837 [details] ck-sources-2.6.16_p12.ebuild remove K_PREPATCHED and UNIPATCH_STRICTORDER to allow ck-patchset to get applied first followed by gentoo patches. Thanks, dsd, for helping me resolve this. With revised order, some genpatches won't apply, 2500, 2505, and 2605. As of now, no need for new variable to affect patch order. For some reason, the two now-removed variables were held over. They are not needed.
Created attachment 88839 [details] ck-sources-2.6.16_p12.ebuild mistakenly had 2505 in exclude list, but that patch does not exist. my bad.
fwiw, it's possible to include the extras patchset as well with the following exclusions: 4200 4205 (fbsplash and vesa-tng), and 4405 (alpha-sysctl-uac.patch). The fbsplash patch requires -F3 in order to patch, and it works. The beyond-sources contain the fbsplash and vesa-tng patches. See bug #103354. Maintainer may wish to consider testing and using. K_WANT_GENPATCHES="base extras" UNIPATCH_EXCLUDE="${UNIPATCH_EXCLUDE} 10 2500 2605 4200 4205 4405" are the lines that need changing. A consideration would be to create a separate local use flag to control whetner either or both of the genpatches get applied. The result of this would be a hybrid ck and gentoo kernel. Pretty neat.
MY_P is not used. Can remove. Or, if you need to keep it, have it contain the ck## revision so it can inserted into EXTRAVERSION. # A few hacks to set ck version via _p instead of -r MY_P=${PV/*_p/} # replace this into EXTRAVERSION below MY_PR=${PR/r/-r} MY_PR=${MY_PR/-r0/} EXTRAVERSION=-ck${MY_P}${MY_PR} KV_FULL=${OKV}${EXTRAVERSION} KV_CK=${KV_FULL/-r*/}
Created attachment 88945 [details] ck-sources-2.6.16_p12.ebuild Cleanups: put description and homepage at top, remove unnecessary MY_P variable. Enhancement: Added patches from gentoo extra and proper excludes.
Peter, Is it safe to try your ebuild for ordinary (like me) user?
(In reply to comment #9) > Peter, > > Is it safe to try your ebuild for ordinary (like me) user? > I have compiled and run the ck12 sources and have noticed no problems. Obviously, keep your current working kernel in your lilo/grub configuration in case you get a panic. But if you have been using ck11, this does not have big differences.
(In reply to comment #10) > I have compiled and run the ck12 sources and have noticed no problems. > Obviously, keep your current working kernel in your lilo/grub configuration in > case you get a panic. But if you have been using ck11, this does not have big > differences. > Thanks, I'm under p12 now (~x86).
2.6.17-ck1 is out now.
I tried hacking in the fbsplash and vesatng patches, but they absolutely are not working with this version -- even with iphitus' hack. So, the new version will still not include the framebuffer splash patches. Maybe spock (hint, hint) will get a chance to look at it. The beyond-sources4.1 are based on ck11 set, and they contain the fbsplash.
Created attachment 89547 [details] ck-sources-2.6.17_p1.ebuild please consider these unofficial as they have not been reviewed by the kernel team. Especially wrt the application and exclusion of genpatches.
*** Bug 137310 has been marked as a duplicate of this bug. ***
Sorry I have been a bit MIA for the last week or two, I'll get this bumped in portage shortly. As for the interest in putting fbsplash and vesa-tng into ck-sources it's not going to happen, sorry. There was a developer maintaining an out of portage ebuild for that but I think he stopped a while back. You are perfectly free to patch it in yourself of course but will require resolving a few patch failures usually.
/me actually reads the bug correctly this time around. Peter, I missed that you were suggesting having all of extras except for fbsplash and vesa-tng added in. I'm going to continue using only 'base' as this is simply supposed to be the ck patchset and base is only there to make it easy to pull in security and serious bug fixes. Thanks for cleaning up the ebuild. STRICTORDER and PREPATCHED were left over from before I started maintaining the ebuild and I never bothered to look at what they were doing :-P 2.6.16-ck12 and 2.6.17-ck1 are now in CVS.
