On 08/17/2012 04:19 PM, "Tóth Attila" wrote:
That is exactly what hardened sources package maintainers do. There's always a tiny time difference between the latest grsecurity patch showing up on the homepage and the respective kernel ebuild appears.
I try to get most of upstream's releases into portage so we can test them as ~arch and give upstream feedback. After a while, I see what issues came up in the last "batch" of kernels. I then pick the one that is least problematic.
Typical upstream cycle goes: 1) introduced new feature, 2) bad breakage, 2) still breakage, 3) not so bad, 4) fixed. I try catch it at #4 before they start the cycle all over again.
Hope this helps to explain my release policy. -- Anthony G. Basile, Ph. D. Chair of Information Technology D'Youville College Buffalo, NY 14201 (716) 829-8197
