Well, I was just curious... so I eventually switched to hardened and right now I'm rebuilding my whole world (>1000 pkgs ^^). I've successfully built your 4.8.7 kernel with grsecurity, pax, debian, suse, fedora, mageia, zen, pardus and branding use flags. Looks great so far. I'll let you know about the exact outcome when I'm done.

I just compiled the geek-sources kernel and all went well, so I removed gentoo-sources. But I am using the binary ati-drivers for the GPU and when I try to reinstall this driver portage tries to install gentoo-sources again.

What is advised in this case? Shouldn't ati-drivers compile against any available kernel sources? Is it needed to maintain gentoo-sources and geek-sources installed?

So all of these patches: aufs (git), bfq (http), fedora (git), gentoo (svn), grsec (git), ice (http), mageia (svn), suse (git) henceforth be set up a local mirror in ${DISTDIR}/geek/<patch name> And based on given versions (in ebuild) from local mirror will be formed themselves patches.

In init6/sys-kernel/geek-sources/files will remain only branding and fix

5) Leave your proposals

Any help, patches are welcome.

P.S.: All these features are ready!!! Now I am testing a them.
P.S.S.: Sorry for my English.

1) About "older" kernel versions less than 3.9 - in fact, their support is still there. But we need to fix the work with git.
Now suse use current stable branch. For the "old" versions of the kernel for suse need to retrieve patches from the same branch stable but older and meet the required version of the kernel.

When replacing values ​​of variables rest on the idea should work fine… But it needs to checked.

2) I would like to leave a zen… but How to simplify getting individual patches?

3) So it would be necessary to do from the start.

4) Now aufs, bfq, fedora, gentoo, grsec, ice, mageia, suse works like 9999 ebuild`s.
Errors can occur in synchronization due to the DISTDIR variable.
Also need to add depending git, svn, sed… and what else could I miss.
Additionally i need assistance any of sed hacker. To optimize this horror:

ls -1 /usr/portage/distfiles/geek/suse/ | grep patches
patches.apparmor
patches.arch
patches.drivers
patches.fixes
patches.kernel.org # <-- do not need. will be skipped if we leave it. so…
patches.rpmify # <-- fixes for build with rpm. we do not need it.
patches.suse
patches.xen # <-- is often cause an error

So patches.kernel.org and patches.rpmify from suse simply delete.

I noticed if all the patches from patches.xen applied without error - kernel build fine. And it is probably more correct in this case it would be fix function ApplyPatch or even make a new function… At present, the function ApplyPatch does not monitor whether all patches from the list of applied without errors.

Need a function that would be tested for a list of patches to correctness of apply all files from the list and a possible error rolls back any changes made to the list of patches. (yep patch -p1 -R < but for all current list)

And for patches.xen it would be just perfect!

khayyam wrote:

init_6 wrote:

[....]
this need to allow line break in variable GEEKSOURCES_PATCHING_ORDER from user file /etc/portage/kernel.conf