| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
On 07/01/2013 01:35 PM, Tom Wijsman wrote: |
| 5 |
> On Mon, 01 Jul 2013 12:20:09 -0400 |
| 6 |
> "Rick \"Zero_Chaos\" Farina" <zerochaos@g.o> wrote: |
| 7 |
> |
| 8 |
>> Some patches are reasonably easy to combine, such as genpatches and |
| 9 |
>> aufs. Some patches are difficult to combine, such as hardened and *. |
| 10 |
>> When you combine hardened patches and aufs (for example) you need |
| 11 |
>> extra patches. I would be THRILLED to see the number of sources cut |
| 12 |
>> down, but hardened-sources must be it's own thing (that said, I'll |
| 13 |
>> personally maintain the aufs patches for hardened if they wanted to |
| 14 |
>> add a USE=aufs flag). |
| 15 |
> |
| 16 |
> Yes, gave it as an quick example but I indeed remember from going |
| 17 |
> through the sources ebuilds that hardened ebuilds do quite some things. |
| 18 |
> I think the downside from extending genpatches is that hardened-sources |
| 19 |
> can no longer rely on it, but we'll have to see that as we go forward. |
| 20 |
> |
| 21 |
> I don't think that apart from hardened the optional patches on their own |
| 22 |
> are hard to combine; they each have their own separate goal, I don't |
| 23 |
> see them conflict on anything. If it happens once in a while, we can |
| 24 |
> still maintain them to work together. |
| 25 |
|
| 26 |
Hardened has K_WANT_GENPATCHES="base" which means it already doesn't |
| 27 |
take the extra patches. We could either introduce a new flag for your |
| 28 |
patches like K_WANT_GENPATCHES="base extra geek" or more likely make |
| 29 |
each one with their own name so that hardened et al can take what they |
| 30 |
like and leave the rest. |
| 31 |
> |
| 32 |
> Also note that I do not plan to introduce any USE flags, since that |
| 33 |
> would duplicate the options to be listed in the kernel menuconfig. |
| 34 |
|
| 35 |
Good point. |
| 36 |
|
| 37 |
Thanks, |
| 38 |
Zero |
| 39 |
> |
| 40 |
>> If users want a vanilla kernel, they want vanilla-sources. Nothing |
| 41 |
>> about that should change. I don't feel that it would be honest to |
| 42 |
>> add a vanilla use flag to gentoo-sources as in no reality are those |
| 43 |
>> vanilla. |
| 44 |
> |
| 45 |
> Apart from the changes discussed on the gentoo-kernel ML, nothing else |
| 46 |
> there will change. You can read the thread as well as the summary; if |
| 47 |
> you disagree, you're welcome to join the discussion there. |
| 48 |
> |
| 49 |
> http://thread.gmane.org/gmane.linux.gentoo.kernel/697 |
| 50 |
> |
| 51 |
> http://thread.gmane.org/gmane.linux.gentoo.kernel/697/focus=730 |
| 52 |
> |
| 53 |
> But yes, apart from that, vanilla-sources will give you vanilla kernel. |
| 54 |
> |
| 55 |
> |
| 56 |
|
| 57 |
-----BEGIN PGP SIGNATURE----- |
| 58 |
Version: GnuPG v2.0.19 (GNU/Linux) |
| 59 |
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ |
| 60 |
|
| 61 |
iQIcBAEBAgAGBQJR0cHKAAoJEKXdFCfdEflKwOYQAIArPK7SsJ6M9BFCuhf/bFOg |
| 62 |
yZfVpSRR8UJgl7as6FsVg4q48NFuFh3lm8PQK792IraccXkYjk/kBGY6IyDt3rUY |
| 63 |
yXHberr53cBZKPC0PPVzDo7ER73GWkobrd+vDrtRHeTJEaPQknvOEmQFBnjY181o |
| 64 |
8uTqQi2VtTnWPP2PeIkqdobkasUcf5lDDXdrvX+ipN+oOSSZ0VJK+XfdlstgrRnH |
| 65 |
o7sESjKm7RbvxQFizzGuE7gOh9GFtIY92zpQVUO4L4P/L5NrGz0yqyor0WYKuUhN |
| 66 |
dZ3k84FQ5SDyKCdCMq/JPKS8jj47gFIkZwfArwKNsRsxkBtcsFHQuj2VXSx0MEcp |
| 67 |
aKv5FfZCj4iSUAg2uwKVfVonyn5qt73Fm+XquxjfbEaT4oTq0FFCL5zjCuf1Zzpt |
| 68 |
3/VOer5N5xu5gY0y6Yt5w7ionHLAFWqXgJF7s/sC7L9eJNHT3XiQtZSPxLGeAkG8 |
| 69 |
beM9PNt7fdYzQAudbi6NZiJ35ZwZQrQfKEAc16hbcH0qDd7ndTWqg0nELX3ulL2z |
| 70 |
FbeCMM0J+tmZ8lEgRriUL7Ki/een1DJX4eCQhYbKIMYKdxDeEMkbZ8N/T3dAWtxm |
| 71 |
IivIs4tTK9EWBF6+8kmUINszCQBsLI6P50TzocqHV+Tj/RyCmeJnOia7DLTD0HGg |
| 72 |
53QUb/jcDjkTF34HbUdG |
| 73 |
=gsg9 |
| 74 |
-----END PGP SIGNATURE----- |
Archives