| 1 |
On Thu, Apr 27, 2017 at 11:45 AM, Manuel Schönlaub |
| 2 |
<manuel.schoenlaub@×××××.com> wrote: |
| 3 |
> Hi, |
| 4 |
> |
| 5 |
> i just have a question regarding packages using linux-info.eclass to check |
| 6 |
> for specific kernel config flags (e.g. app-emaulation/docker). |
| 7 |
> |
| 8 |
> Currently it seems like the flags are only checked against the config in |
| 9 |
> /usr/src/linux which is not necessariliy the running kernel. |
| 10 |
> |
| 11 |
> Furthermore there are some warnings printed, but after some time i find it |
| 12 |
> hard to remember what i will have to change in my kernel configs in order to |
| 13 |
> make the package work right. It is also just a snapshot of the situation at |
| 14 |
> the time emerge is building the package. |
| 15 |
> |
| 16 |
> Does there exists a tool helping in maintaining consistency between kernel |
| 17 |
> configuration and configs required by currently installed packages. |
| 18 |
> |
| 19 |
> If not, could emaint be be the right tool to extend with this functionality? |
| 20 |
> Or is this functionality not really needed? |
| 21 |
> |
| 22 |
> Regards, |
| 23 |
> |
| 24 |
> Manuel |
| 25 |
|
| 26 |
I too run custom rather than gentoo kernels on my system with |
| 27 |
/usr/src/linux being a symbolic link pointing to the location of the |
| 28 |
kernel sources I have in my $HOME directory for this very reason. |
Archives