On Wed, Nov 27, 2002 at 11:19:00PM +1100, Keith Owens wrote:
> Bullshit. It was fully documented in kbuild 2.5. Just because Kai
> dropped the docs when he stole bits from kbuild 2.5 does not make
> .force_default into an undocumented feature.
I never seen this as a standalone patch from you - something i missed?
I do not remember exactly but I may have been the person
extracting this from kbuild-2.5 and feeding this patch to Kai,
in which case you should blaim me, not Kai.
If you were not properly attributed at that point in time, sorry for that.
If kconfig are extended with functionality similar to .force_default
then the file containing the defaults shall NOT be hidden.
There is no good reason to hide for the user that some options
are forced to a specific value.
IIRC the old implementation only impacted "make oldconfig", so
doing something like:
echo CONFIG_HOTPLUG=y > .force_default
make oldconfig
make menuconfig, enable HOTPLUG
Manually tweak .config and run make oldconfig
then I would behind my back loose the hotplug setting, without
any warning.
If implemented defaults should be effective in all frontends, not only
make oldconfig. Forced defaults should be unchangable in the frontends.
It is not intuitive for the user that at one point something is forced
enabled, and then later the user are anyway allowed to change it
without further notice.
Sam
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Sat Nov 30 2002 - 22:00:18 EST