In article <[EMAIL PROTECTED]> you wrote: > [-- text/plain, encoding quoted-printable, charset: us-ascii, 29 lines --] > > Just had a look at the 2.6.14 kernel image packages, and this is still a > problem. > > The .extraversion file that exists is not read by anything in the kernel > makefiles supplied in the linux-headers package that I can see... > > "ln .extraversion localversion-debian" makes the module install scripts > from the kernel work properly, but this is not completely correct > behaviour since it's an extraversion, not a localversion, but this > happens to work... > > Perhaps localversion-00debian would be better, to be sure it's first > ahead of any other patches applied, but ideally the value should be in > the Makefile as EXTRAVERSION, which would mean it could no longer be > shared amongst the linux-headers-2.6.14-2-* packages. > > Another option would be modify the upstream Makefile to read > .extraversion into EXTRAVERSION at the top of the Makefile... It's > Debian-specific, and probably not the best solution given that there > appears to be scripts out there reading .extraversion, eg. #333842. But > it otherwise seems a good solution to me that doesn't require unsharing > the Makefile.
Manoj, being the extraversions expert, do you have any thoughts on this. The current situation seems less than ideal. -- Horms -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]