| 1 |
Hi everyone, |
| 2 |
|
| 3 |
|
| 4 |
== Brief summary of this project == |
| 5 |
|
| 6 |
kernelconfig is about generating kernel configuration files, |
| 7 |
using various sources such as curated defconfigs, detected hardware, |
| 8 |
installed packages and user input. |
| 9 |
|
| 10 |
The project's code can be found at [0]. |
| 11 |
|
| 12 |
|
| 13 |
== This week's progress == |
| 14 |
|
| 15 |
The documentation has been updated to cover "hardware detection". |
| 16 |
|
| 17 |
Package management integration is mostly done. |
| 18 |
The pm-information stems from linux-info.eclass' CONFIG_CHECK variable. |
| 19 |
kernelconfig uses portage's Python API to determine which relevant packages |
| 20 |
are installed and retrieves their build-time CONFIG_CHECK value. |
| 21 |
Since the build-time value is likely to have been compared against a different |
| 22 |
kernel sources tree, it is also possible to re-evaluate CONFIG_CHECK |
| 23 |
by running the appropriate ebuild phases in a temporary overlay specifically |
| 24 |
created for that purpose. |
| 25 |
|
| 26 |
|
| 27 |
== Plans for the next week == |
| 28 |
|
| 29 |
Documentation and code improvements. |
| 30 |
|
| 31 |
|
| 32 |
[0] https://github.com/dywisor/kernelconfig |
| 33 |
|
| 34 |
Regards, |
| 35 |
André E. |
Archives