I thought about this and guessed I should look at m-a's wishlist before
thinking too much :) Note that I didn't find a debian-devel thread about
this.
First, a little note about why this came to me too so why it would help.
I did an InstallFest yesterday and someone wanted NVIDIA's 3D driver (of
course...). He was on testing, running 2.6.12. At sometime 2.6.12 will
be discontinued and he'll have to update to avoid using a holed kernel.
He won't have to repeat the whole NVIDIA install procedure I did, but if
he doesn't do or forget about the m-a part, he won't be able to use the
new kernel without reconfiguring X (he can do nearly nothing in
console). I wish I could have told him "When the kernel upgrades, it
should work.", instead of giving him my email in case he can't fix it
(yeah yeah, m-a is already simple. but just in case).
Now a thought about implementation : the method I imagined by myself was
hooks in kernel packages. But I can see issues if only the init scripts
method is implemented. If m-a is used to compile network drivers (like
it is on my laptop...), and this driver is needed for the primary
interface to access the net, compiling the drivers in the new kernel may
be painful if stuff needs to be downloaded (corresponding kernel headers
and updated modules source packages come to mind).
Sean seems to suggest implementing both methods in his last mail. That
may be a good idea too.
In any case, having one method implemented would be pretty useful :)
You're doing great job on m-a, Eduard.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
