Re: kernel configuration management tool
Sven Luther <luther@debian.org> writes:
>> What's the planned features for it?
>
> The idea is to parse the Kconfig, and generate a graph, which represents all
> the Kconfig dependencies (and conditions), multiplied by each
> arch/subarch/flavour we have.
>
> This would lead to a representation of all the Kconfig related info we have
> both in the kernel and in debian/arch.
>
> Then we can do various things, like building such a graph for the old and new
> version, and produce a diff, like what kconfig.ml -d does for a single
> arch/subarch/flavour, or diff different branches of the arch/subarch/flavour
> tree.
>
> We can also check for consistency of the debian config tree, check if there
> are missed options which are auto-filled by the kernel kconfig tool, and so
> on.
>
> Furthermore, this would lead to the writing of an interactive (ncurse based ?)
> tool for setting those configuration options, or maybe a pure text
> oldconfig-like tool.
>
> The next step of this process would be to parse the Makefiles, in order to
> detect the modules which are build from the given config option, so we can
> detect new modules or removed modules corresponding to Kconfig options which
> changed. Or in general offer as information in the tool about the modules
> which are affected by a config option.
>
> Finally, if this idea is taken to the end, this mean we can even provide a way
> for at least providing hint of changed modules from one kernel version to the
> next, in order to make kernel-wedge / module .udebs management easier.
I agree that it's difficult to change any current tool to make this. I
like the proposal a lot :-D
--
O T A V I O S A L V A D O R
---------------------------------------------
E-mail: otavio@debian.org UIN: 5906116
GNU/Linux User: 239058 GPG ID: 49A5F855
Home Page: http://otavio.ossystems.com.br
---------------------------------------------
"Microsoft sells you Windows ... Linux gives
you the whole house."
Reply to: