1 |
On 06/10/2014 01:50 PM, Anthony G. Basile wrote: |
2 |
>> |
3 |
>> Can linux-info.eclass be used to spit out a warning during a python emerge? |
4 |
>> |
5 |
>> This, |
6 |
>> |
7 |
>> use hardened && CONFIG_CHECK+=" ~CONFIG_PAX_EMUTRAMP" |
8 |
>> |
9 |
>> seems like a common pattern. With a little more ingenuity we can |
10 |
>> probably have it check the running/installed kernel and not the USE flag. |
11 |
>> |
12 |
> |
13 |
> Yes and no. I could add that as a warning but .... There is no |
14 |
> guarantee that the kernel you are building under is the kernel you will |
15 |
> be running under. So there's no way to warn against future stupidity. |
16 |
> Or current stupidity if your running kernel and kernel sources are out |
17 |
> of sync. |
18 |
> |
19 |
> So I'm not a fan of linux-info.eclass. |
20 |
> |
21 |
|
22 |
It's not 100%, but it has to be more accurate than manually replying to |
23 |
each bug report, right? |
24 |
|
25 |
I think it's easy to overestimate the number of corner cases that normal |
26 |
users run into with their kernels. Even on my home/work desktops, which |
27 |
are a mess, most of the kernels that are lying around are pretty much |
28 |
the same. If one of them has EMUTRAMP set, the rest do. |
29 |
|
30 |
This might even be done once and for all in pax-utils.eclass. If a |
31 |
package needs an -E marking, the user will probably want EMUTRAMP set at |
32 |
runtime. |