On Thu, Jul 19, 2012 at 06:30:47PM +0100, Alan Cox wrote:
Well, yes. I was thinking it would be more like:
distro/Kconfig.fedora menuconfig FEDORA if FEDORA config FEDORA_16 select WHATEVER config FEDORA_17
Nope you need
distro/everyarchtheyship/everykernelvarianttkeyship(smp,largemem,arm boards)/Kconfig
which for some distros is over 20 per release and the end user wouldn't have a cat in hells chance of knowing which to pick.
20? Debian's kernel package currently lists 17 architectures (11 source architectures) and 44 variants (excluding PREEMPT_RT and s390 install tape). (But 'only' 31 will be in the next release, as even Debian is capable of letting go of an architecture.) But, assuming a native build (a whole weekend's worth of fun on m68k!) we already know the target architecture and most of the other variations can be chosen automatically similarly to localmodconfig. We already do something like that (choosing between the pre-built variants) at distribution install time, after all.
For the end user case you need the distro to plonk the right file in the right place and be done with it, once they do that the rest is bikeshedding a ten line Makefile rule.
This might work well for future releases; is there not a need to make this work for past releases too? Ben. -- Ben Hutchings We get into the habit of living before acquiring the habit of thinking. - Albert Camus -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org