On 8/4/2010 6:21 AM, Igor Stoppa wrote:
On 08/04/2010 03:39 PM, ext Arjan van de Ven wrote:
config-generic is the set of defaults
yes ...
the platform specific configs are overrides to these defaults, so that
the platform specific configs don't HAVE to deal with every config
option.
but in practice they _have_ to when the product is not interested in
stuff pulled in by config-generic
they can if they want to... that's why it's an override.
I guess what i'm really after is the fact that config-generic should
rather be config-minimal, including basic stuff to get a command
prompt and the rest could be left to platform customization.
At least wrt the embedded space.
Probably your approach is better suited for laptop-like devices which
have more standardized sw.
actually, especially in the embedded space we need something like this
there's no way we can scale having to update 15 to 30 kernel config
files individually every time there is a new config option.
and MeeGo as a project, with its charter, isn't about doing the super
customized embedded thing; the whole point of MeeGo is to provide
an as consistent as possible environment to developers between devices,
while keeping a rich and attractive environment.
Consistency doesn't stop at the kernel syscall layer; to provide
consistency the kernels between devices should also be as consistent as
possible....
and yes some space gets sacrificed for that... but that is true
throughout the whole stack.
MeeGo phones will have components that aren't strictly needed for phone,
but are there for other device categories.
MeeGo IVI will have the 3G phone components that they have no use for,
to stay consistent
etc etc.
_______________________________________________
MeeGo-dev mailing list
[email protected]
http://lists.meego.com/listinfo/meego-dev
