Re: Modules packaging policy - call for discussion
On Fri, Mar 24, 2006 at 01:16:45AM -0500, Joey Hess wrote:
> (Your use of the term "udeb kernels" is confusing and innaccurate. d-i
> does not use different kernels than anything else.)
Indeed, point taken. To clarify: I meant the udeb packages
kernel-image-$KVERS-di.
> Max Vozeler wrote:
> > 2. The information about flavours used in udeb kernels is not
> > available in linux-headers. For normal flavours waldi's build
> > infrastructure (and my homebrewn scripts) use the information in
> > /usr/src/linux-headers-$VERSION/arch/ to look up availablea
> > flavours. Information about udeb flavours cannot be looked up in
> > the same way. So at the moment I maintain a list of udeb flavours
> > by hand and watch d-i commits to notice changes [0].
> No idea what you're talking about here
Let me try again: In order to build module packages for Debian
kernel packages and the repackaged -di kernel packages, I need to
know at build-time which flavours my package should try to build
for so that I can generate debian/control accordingly. This
information is available in the configs included in the arch/
directory of linux-headers packages. -di kernel packages, however,
use only a subset of these flavours. My question is: How can I
determine the subset of flavours that are used in -di packages
and that it makes sense to build module udebs for?
> and your footnote is dangling.
[0] This is what I ended up doing in the source package
loop-aes-modules. I hope to replace the scripts with waldi's
infrastructure as soon as I manage to solve this point.
cheers,
Max
Reply to: