On Wed, Apr 21, 2010 at 04:22:47PM +0300, Roger Quadros wrote: > ext Arjan van de Ven wrote: >> On 4/21/2010 0:22, Roger Quadros wrote: >>> ext Arjan van de Ven wrote: >>>>> +n900: kernel.spec.in series makespec.pl >>>>> + @touch N900; >>>>> + @perl makespec.pl< kernel.spec.in> kernel-n900.spec ; >>>> why make a separate spec like this? sounds completely unneeded to me.... >>>> for arm it will only build the n900 anyway right now >>> In future we should see more ARM platforms. we cannot say that arm = N900. >> >> so? just stick it in kernel.spec. >> >>> Currently config-generic is more x86 specific it even has ARCH=x86. >>> so currently config-generic is broken. >> >> so fix it ? But what you mention is not broken. It's by design. >> config-generic is the superset of all config options. >> >>> And how can we ensure that this config-generic is compatible to all >>> platforms? >> >> I think you misunderstood; config-generic is the basis for the configs, and >> architectures override >> individual pieces they need.... and then the board config overrides on top >> of that. >> and any option that does not actually exist for the platform will go away >> automatically. >> > > Isn't it simpler to have one config file per variant than doing this > automagical merging with 3 config files?
As someone who has maintained kernels with a few dozen config files for a long time, for different arches and flavors, no, this seems much easier to keep everything in sync properly. Let's try it and see, individual config files are very hard to ensure that they are consistant. thanks, greg k-h _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev
