DESKTOP mode
Bernhard Fischer
rep.nop at aon.at
Mon Oct 2 12:17:37 PDT 2006
On Sun, Oct 01, 2006 at 10:04:29PM -0400, Paul Fox wrote:
> >
> > The idea is that we don't want to drown in CONFIG_applet1_FEATURE_x,
> > CONFIG_applet1_FEATURE_y, CONFIG_applet1_FEATURE_z, CONFIG_applet2_FEATURE_x,
> > CONFIG_applet2_FEATURE_y, CONFIG_applet2_FEATURE_z...
> > There are just farr too many of them.
> >
> > Everything which is not likely to be ever needed on
> > the embedded device, is covered by single CONFIG_DESKTOP
> > (gzip -v is a good example).
> >
> > However, if some option is under CONFIG_DESKTOP but then
> > someone feels [s]he really needs to be able to toggle
> > it separately, okay, send a patch which
> > (1) introduces new CONFIG_GZIP_FEATURE_V
> > (2) changes code to be conditionally compiled under it and
> > (3) adds "select CONFIG_GZIP_FEATURE_V" to CONFIG_DESKTOP entry,
> > so that selecting CONFIG_DESKTOP=y automagically turns it on too.
> >
> > IOW: introduce individual CONFIGs on as-needed basis.
>
>i think lumping a whole lot of unrelated options under a single
>vague heading like "desktop" (what's that mean, anyway?) is
>silly. it's one thing to have separate options, and to put them
>all under one config menu, or even to have a meta-option that
>selects a whole lot of them for you (kind of like bareconfig,
>allconfig, defconfig: i.e., "make desktopconfig". but putting them
>all together under one ifdef is just being lazy.
Seconded.
A meta option sounds about ok, but i, personally don't think a
catch-em-all option is suitable approach for a project like busybox.
More information about the busybox
mailing list