| 1 |
On 04/27/2017 10:45 AM, Manuel Schönlaub wrote: |
| 2 |
> Hi, |
| 3 |
> |
| 4 |
> i just have a question regarding packages using linux-info.eclass to |
| 5 |
> check for specific kernel config flags (e.g. app-emaulation/docker). |
| 6 |
> |
| 7 |
> Currently it seems like the flags are only checked against the config |
| 8 |
> in /usr/src/linux which is not necessariliy the running kernel. |
| 9 |
> |
| 10 |
> Furthermore there are some warnings printed, but after some time i |
| 11 |
> find it hard to remember what i will have to change in my kernel |
| 12 |
> configs in order to make the package work right. It is also just a |
| 13 |
> snapshot of the situation at the time emerge is building the package. |
| 14 |
> |
| 15 |
> Does there exists a tool helping in maintaining consistency between |
| 16 |
> kernel configuration and configs required by currently installed packages. |
| 17 |
> |
| 18 |
> If not, could emaint be be the right tool to extend with this |
| 19 |
> functionality? |
| 20 |
> Or is this functionality not really needed? |
| 21 |
> |
| 22 |
> Regards, |
| 23 |
> |
| 24 |
> Manuel |
| 25 |
It does not directly help with the consistency problem, but Elogv |
| 26 |
(https://wiki.gentoo.org/wiki/Elogv) at least helps to keep track of the |
| 27 |
messages portage prints out. You could, for example, decide to not |
| 28 |
remove the messages with kernel config changes that you have not done, yet. |
Archives