dependency checking in copy-modules (linux-kernel-di)

[Gaudenz Steinlin <gaudenz@soziologie.ch>]

Hi joey and others

I'm trying to make linux-kernel-di usable for arch!=i386. 

I first tried to understand the dependency checking code in
copy-modules, but it probably needs a degree in rocket-science to
understand that completely. But as far as I understood it, dependencies
are only checked based on module-deps which declares dependencies
between module-udebs. I didn't see any code that checks the actual
dependencies between the kernel-modules. So I asked myself why all this
dependency checking code is needed. Isn't it enough to declare these
dependency information in debian/control?

The actual problem was, that i wanted to find out, if we need a
module-deps for every arch or not. Probably we will need it, because
dependencies can be different on different archs. Then I wonderd why the
order of the lines in module-deps is important (because i wanted to
simply concatenate the general module-deps and the arch-specific
module-deps)?

Can you (or someone else) please line out the advantages of this
dependency checking and how it works and how it can be ported to
non-i386?

Thanks
gaudenz