config -> default

[Greg Watson]

Stefan,

Which builds are broken? I thought I checked all configurations built 
after the change (apart from the VIA which Ron was working on.) and 
modified any that had problems.

My hope was that this change would make the use of options more 
logical and consistent. The intention is that parts set default 
values for any options that they require or are specific to the part. 
Then when all the parts are put together in a target configuration 
file, these default values can be overridden for the specific build. 
I was also toying with the idea of allowing some options to be 
read-only, which I think would address your concern.

Apologies for breaking things. I try to build all targets after any 
change like this to make sure things are still working.

Greg

At 4:16 PM +0100 11/6/03, Stefan Reinauer wrote:
>Hi,
>
>most of the builds are broken again since "config" in the mainboard
>config file now has to be renamed to "default". On the one hand I see
>the reason for most of these changes, even though I am not sure if
>we want to suggest that some stuff can be overridden in the target
>config file, like:
>
>-option CONFIG_IOAPIC=1
>+default CONFIG_IOAPIC=1
>
>Can those changing elementary stuff like this that breaks all builds try
>to apply some regexps on the Config files so that other builds don't
>break? Getting further is somewhat hard currently since the code almost
>instantly breaks after the last fixes are checked in..
>
>Stefan
>
>--
>      Stefan Reinauer, SUSE LINUX AG
>Teamleader Architecture Development
>_______________________________________________
>Linuxbios mailing list
>Linuxbios at clustermatic.org
>http://www.clustermatic.org/mailman/listinfo/linuxbios