| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
Alexander Berntsen schrieb: |
| 5 |
> On 27/07/13 10:56, Chí-Thanh Christopher Nguyễn wrote: |
| 6 |
>> How about dropping vanilla-sources and adding a "vanilla" USE flag to |
| 7 |
>> gentoo-sources? |
| 8 |
> Then we might as well just have a Linux package with a bunch of USE |
| 9 |
> flags -- gentoo, hardened, libre, tuxonice, ck, etc. |
| 10 |
|
| 11 |
I don't think this can be made work, the other kernel packages' releases |
| 12 |
may not happen simultaneously with kernel releases. Or they may even skip |
| 13 |
certain releases. |
| 14 |
|
| 15 |
Rich Freeman schrieb: |
| 16 |
> Unless it were stable-masked it would create the exact same problem. |
| 17 |
|
| 18 |
vanilla flags are not package.use.stable.mask'ed for toolchain packages |
| 19 |
either, yet they go stable with them. And there, USE=vanilla might cause |
| 20 |
serious breakage even. |
| 21 |
|
| 22 |
> There was another suggestion to try to manage the patch sets via the |
| 23 |
> kernel config system, but that isn't without its own challenges. |
| 24 |
|
| 25 |
vanilla = don't apply any patches, I don't think that could be improved by |
| 26 |
any modification to the kernel config system. |
| 27 |
|
| 28 |
|
| 29 |
Best regards, |
| 30 |
Chí-Thanh Christopher Nguyễn |
| 31 |
-----BEGIN PGP SIGNATURE----- |
| 32 |
Version: GnuPG v2.0.20 (GNU/Linux) |
| 33 |
Comment: Using GnuPG with SeaMonkey - http://www.enigmail.net/ |
| 34 |
|
| 35 |
iEYEARECAAYFAlH0D3MACgkQ+gvH2voEPRBmFACbBixGjRbW0z4yOhMvLRXaHx1z |
| 36 |
PjAAnin5cF6lD7X8n0KGpBbyMFT3kAAz |
| 37 |
=kPOS |
| 38 |
-----END PGP SIGNATURE----- |
Archives