Re: Call-for-help: modconf
> What is the long term future with modconf, seems that the
> debian-installer, modconf and kernel-package are all pretty much
> intertwined.
First I want to clarify -- modconf has needs for potato (the point
releases) and woody (even if we don't have a d-i solution), so it
really needs attention very soon.
We need to rethink how we want modconf - aka a kernel modules
configuration utility - to work. As I see it, the biggest problem with
modconf is that there's no easy way to get the description of modules,
so we are left with a hack that is difficult to maintain. We really need
a more robust and maintainable way to handle a modules database. Any
ideas?
randolph
--
Debian Developer <tausq@debian.org>
http://www.TauSq.org/
Reply to: