| 1 |
Em sáb, 25 de jan de 2020 21:34, Adam Carter <adamcarter3@×××××.com> |
| 2 |
escreveu: |
| 3 |
|
| 4 |
> On Sat, Jan 25, 2020 at 12:48 AM Francisco Ares <frares@×××××.com> wrote: |
| 5 |
> |
| 6 |
>> Hi, All. |
| 7 |
>> |
| 8 |
>> I would like to see all pre-merge checks prior to build a new kernel, |
| 9 |
>> just to make sure all kernel configurations needed até satisfied. |
| 10 |
>> |
| 11 |
>> I thought on issuing an "emerge -e world" then interrupting the process |
| 12 |
>> at the beguinning of the first package build. But this looks a weird way |
| 13 |
>> of doing things. |
| 14 |
>> |
| 15 |
>> Is there any other way? |
| 16 |
>> |
| 17 |
>> |
| 18 |
> The command looks through the ebuilds of installed packages and dumps a |
| 19 |
> list of of the kernel options that the ebuilds are looking for, so its a |
| 20 |
> start. You'll then need to check this against your .config file. |
| 21 |
> |
| 22 |
> If you're not using the new $PORTDIR of /var/db/repos/gentoo you'll need |
| 23 |
> to change that of course. |
| 24 |
> |
| 25 |
> for pak in $(qlist -ICv | sed |
| 26 |
> 's/\(.*\)\(\/.*\)\(-[0-9].*\)/\1\2\2\3.ebuild/g' ); do grep -s -H |
| 27 |
> 'CONFIG_CHECK="' /var/db/repos/gentoo/$pak ; done |
| 28 |
> |
| 29 |
> |
| 30 |
> |
| 31 |
> This is awesome! |
| 32 |
|
| 33 |
Thank you! |
| 34 |
|
| 35 |
To check out what the developer think it is really important, there's the |
| 36 |
ERROR_ string to grep for. |
| 37 |
|
| 38 |
Best Regards, |
| 39 |
Francisco |
| 40 |
|
| 41 |
> |
| 42 |
> |
Archives