From: "Randy.Dunlap" <rdunlap@xenotime.net>
To: Roman Zippel <zippel@linux-m68k.org>
Cc: hirofumi@mail.parknet.co.jp, linux-kernel@vger.kernel.org,
sam@ravnborg.org
Subject: Re: [RFC/POC] multiple CONFIG y/m/n
Date: Wed, 12 Apr 2006 09:17:51 -0700 [thread overview]
Message-ID: <20060412091751.feba2dd4.rdunlap@xenotime.net> (raw)
In-Reply-To: <Pine.LNX.4.64.0604121253540.32445@scrub.home>
On Wed, 12 Apr 2006 13:00:22 +0200 (CEST) Roman Zippel wrote:
> Hi,
>
> On Sun, 9 Apr 2006, Randy.Dunlap wrote:
>
> > +void usage(char *progname)
> > +{
> > + printf("%s [-o|-s|-d|-D|-n|-m|-y|-r] Kconfig_filename\n", progname);
>
> |-D <config>|
>
> > + printf(" -o: oldconfig: ask only about new config symbols\n");
> > + printf(" -s: silentoldconfig: don't ask about any symbol values\n");
>
> It does ask about them, but suppresses a lot of prints.
>
> > + printf(" -d: defconfig: use default symbol values\n");
>
> To be precise it uses arch/$ARCH/defconfig as default values.
>
> > + printf(" -n: set unknown symbol values to 'n'\n");
> > + printf(" -m: set unknown symbol values to 'm'\n");
> > + printf(" -y: set unknown symbol values to 'y'\n");
>
> It actually tries to set all values to n/m/y.
>
> > @@ -546,8 +564,8 @@ int main(int ac, char **av)
> > break;
> > case 'h':
> > case '?':
> > - printf("%s [-o|-s] config\n", av[0]);
> > - exit(0);
> > + usage(av[0]);
> > + break;
>
> That's indeed a little obsolete. :-)
IMO the main points/questions are:
- where to document the command-line options and environment variables
(including the recent KCONFIG_CONFIG): in a usage() function or in
Documentation/kbuild/usage.txt file?
- if the answer above is in a usage() function, how does a user invoke
that help request? Doing "make config -h" doesn't work: 'make' sees
the -h and spits out its own help text. Would a special case of
'make config help' be acceptable or is this a good reason to use
a usage.txt file instead?
- or have you already taken care of all of this? 8;)
Thanks.
---
~Randy
next prev parent reply other threads:[~2006-04-12 16:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-07 5:41 [RFC/POC] multiple CONFIG y/m/n Randy.Dunlap
2006-04-07 15:04 ` OGAWA Hirofumi
2006-04-07 15:45 ` Randy.Dunlap
2006-04-10 5:04 ` Randy.Dunlap
2006-04-12 11:00 ` Roman Zippel
2006-04-12 16:17 ` Randy.Dunlap [this message]
2006-04-12 16:59 ` Sam Ravnborg
2006-04-12 18:56 ` [PATCH] config: update usage/help info Randy.Dunlap
2006-04-12 20:44 ` Sam Ravnborg
2006-04-07 18:44 ` [RFC/POC] multiple CONFIG y/m/n Sam Ravnborg
2006-04-07 21:24 ` Roman Zippel
2006-04-07 21:36 ` Randy.Dunlap
2006-04-11 11:05 ` Jan Engelhardt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060412091751.feba2dd4.rdunlap@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=hirofumi@mail.parknet.co.jp \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.org \
--cc=zippel@linux-m68k.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.