This really surprised me, I just realized, when a user emerging vanilla kernel gets a slightly modified source-code -- why does gentoo change the Makefile of the vanilla-sources? Ok changes in DocBook are clear...but what's this from linux-2.4.22/Makefile: ? 4c4 < EXTRAVERSION = --- > EXTRAVERSION = 77c77 < export INSTALL_PATH=/boot --- > #export INSTALL_PATH=/boot This leads to confusion if a user merges vanilla-sources to *patch* it manually. Patches are rejected - line 4 is different -- it does not look different but it is, because "gentoo-version" of vanilla contain a space-char behind "EXTRAVERSION =" but the original source does not. Please, do not change anything in the vanilla-sources - people would expect to find a really unmodified version if they merge vanilla. I'm not sure, what is causing this change - I guess it could be a portage-bug, since the ebuild uses "kernel_universal_unpack" - and does not change the sourcecode directly in the ebuild.
The INSTALL_PATH is a legitimate change to make "make install" behave correctly. The EXTRAVERSION is a sideeffect of the the sed rule to set the kernel version on patched kernels, it's not easily fixed, but I'll look into it.
This seems to be fixed - I just merged the latest vanilla-sources-2.4.22 to check this and the INSTALL_PATH is no longer commented and the EXTRAVERSION seems to match the true vanilla one...
