Re: [RFC] kernel-headers and /lib/modules/*/build -> ?
>>"Michel" == Michel Dänzer <michdaen@iiic.ethz.ch> writes:
>> A initial cut at the changes involved:
>> 1) the official kernel-image packages do not ship the symbolic link
>> /lib/modules/$(uname -r)/build installed by the kernel makefiles
>> 2) the kernel image package prerm removes the symlink, so that
>> official kernel image packages are removable (and do not leave
>> cruft dirs with a symlink around)
>> 3) Instead of shipping a tarball of kernel headers, we ship unpacked
>> kernel headers. Looking at the Packages files today, installed
>> sizes of kernel-header packages range from 20MB to 32MB.
>> 4) the kernel header postinst is enhanced to look for the link
>> /lib/modules/$VERSION/build, and, if the dir exists but the
>> symbolic link does not exist, create the symlink, pointing to the
>> unpacked kernel headers package.
>>
>> As far as I can see, this benefits people who
>> a) are running the official kerel image
Michel> I don't see the need for discrimination between un/official
Michel> kernel packages in this regard.
Oh, I should dot my i's. Ok. The header package should only
create a symlink if none exists. Only the official images should
ship, by default, without the symlink (I would be very mad if the
symlink pointing to my work tree was removed).
I guess one could ask kernel package not to ship the symlink
in my local kernel image, too; and then also create a header package,
that creates the symlink. All this work so I do not have to unpack a
tarball and create s link?
>> b) who want to build unpackaged kernel modules
>> c) who do not have the real kernel sources around
Michel> For example, I (like a lot of powerpc users) am following an
Michel> rsync tree to build my kernels, so I don't have the source
Michel> for any but the current kernel.
Heh. I use lndir to create a symlink farm, and then build my
kernels in the symlink farm. The real kernel may move on, but the
includes live in the symlink farm for as long as I have the image.
Another advantage is that the real source tree always remains
pure; any experimental/local patches are applied to the symlink farm.
Indeed, the symlink farm i probably a better solution for you
that all this scripted mucking around of the build symlink,and does
not need one to ship unpacked kernel header trees to all the other
users out there.
manoj
--
That is the key to history. Terrific energy is expended --
civilizations are built up -- excellent institutions devised; but
each time something goes wrong. Some fatal flaw always brings the
selfish and cruel people to the top, and then it all slides back into
misery and ruin. In fact, the machine conks. It seems to start up
all right and runs a few yards, and then it breaks down. Lewis
Manoj Srivastava <srivasta@debian.org> <http://www.debian.org/%7Esrivasta/>
1024R/C7261095 print CB D9 F4 12 68 07 E4 05 CC 2D 27 12 1D F5 E8 6E
1024D/BF24424C print 4966 F272 D093 B493 410B 924B 21BA DABB BF24 424C
Reply to: