> > Finding that you cannot rebuild a package, that built perfectly > > yesterday, simply because you decided to have a look at the latest > > kernel source, is very depressing. > > Any Joe User will expect the correct headers to be in place. Any user > that is building unstable kernels will know better than to place the > headers where they might cause problems.
So are you suggesting that kernel_image packages should contain the headers with which the kernel was built ? So that if you installed a new kernel package, you could guarantee that the headers would match ? >From past experience, I'd say that this was a bad idea, because it can make one's development environment unstable. Anyone who is building software that really is kernel version dependent, is actually helped IMO by the fact that while they're building it, the -I/usr/src/linux/include that appears on each compilation acts as a mnemonic for ``This is kernel version dependent software''. This also makes the same fact clear to anyone who is wondering why they cannot build the same binaries on a different system. People who are building software that isn't very kernel version sensitive can really do without destroying their development environment, just because they've installed a new kernel. Cheers, Phil.
