Re: [RFC PATCH] kconfig: use long options in conf

[Aristeu Rozanski <aris@redhat.com>]

On Thu, Jul 29, 2010 at 05:04:57PM +0200, Michal Marek wrote:
> On 29.7.2010 16:47, Aristeu Rozanski wrote:
> > On Thu, Jul 29, 2010 at 11:23:49AM +0200, Michal Marek wrote:
> >> On 29.7.2010 10:13, Sam Ravnborg wrote:
> >>> On Wed, Jul 28, 2010 at 10:36:22PM +0200, Sam Ravnborg wrote:
> >>>> Hi Michal.
> >>>>
> >>>> I cooked up the following to introduce long options in conf.
> >>>> But in the process I dropped the short options. Is this OK?
> >>>
> >>> On top of this patch I did another two.
> >>> They fixup the *nonint_oldconfig targets:
> >>>
> >>> nonint_oldconfig:
> >>> - renamed to listnewconfig
> >>> - print new options to stdout (to better support redirect)
> >>> - no longer saves a new configuration
> >>> - does ot exist with a failure code if there is new options
> > but this kills its usefulness. nonint_oldconfig is used so you can script
> > the use of a generated configuration (think distro kernel RPMs). if something
> > is not set, it fails listing what's not set. otherwise it'll save the
> > configuration and whatever script is using it can proceed.
> > "listnewconfig" is a new, different target to me.
> 
> How about
> new=$(make listnewconfig)
> if test -n "$new"; then
>     echo "Please set the following options:" >&2
>     echo "$new" >&2
>     exit 1
> fi
> ? Wouldn't that be the same as nonint_oldconfig before?
what's the other use cases for listnewconfig (other than a incomplete
nonint_oldconfig)?

-- 
Aristeu