From: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
To: Alexander Kanavin <alex.kanavin@gmail.com>
Cc: John Ogness <john.ogness@linutronix.de>,
OE-core <openembedded-core@lists.openembedded.org>,
Alexander Kanavin <alex@linutronix.de>
Subject: RE: [OE-core] [PATCH 1/2] oe-setup-build: add a tool for discovering config templates and setting up builds
Date: Tue, 6 Sep 2022 12:25:48 +0000 [thread overview]
Message-ID: <6632fb17a872496ea3b7a61a42f2ae06@axis.com> (raw)
In-Reply-To: <CANNYZj_sTxPuZtdVk68A8AGqwnT6=RNXmJ6u1LVuc6BQiHRvkw@mail.gmail.com>
> -----Original Message-----
> From: openembedded-core@lists.openembedded.org <openembedded-
> core@lists.openembedded.org> On Behalf Of Alexander Kanavin
> Sent: den 6 september 2022 13:32
> To: Alexander Kanavin <alex.kanavin@gmail.com>
> Cc: John Ogness <john.ogness@linutronix.de>; OE-core <openembedded-
> core@lists.openembedded.org>; Alexander Kanavin <alex@linutronix.de>
> Subject: Re: [OE-core] [PATCH 1/2] oe-setup-build: add a tool for
> discovering config templates and setting up builds
>
> On Tue, 6 Sept 2022 at 13:24, Alexander Kanavin via
> lists.openembedded.org <alex.kanavin=gmail.com@lists.openembedded.org>
> wrote:
> > > 4. Listing available templates is a nice feature, but this alternate
> > > mode of operation should have its own argument. Something like
> > >
> > > -l List available build configuration templates.
> >
> > See above please.
>
> On second thought... the two modes of operation should be more clearly
> separated, perhaps with git-style subcommands. As long as the default
> without arguments remains discovery :)
>
> Alex
Given that the tool is called oe-setup-build and not oe-discover-build,
making the discovery mode the default is actually a bit weird.
Subcommands sounds fine to me though. Maybe you should call it
oe-build-env instead, since it has multiple modes?
//Peter
next prev parent reply other threads:[~2022-09-06 12:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-05 18:21 [PATCH 1/2] oe-setup-build: add a tool for discovering config templates and setting up builds Alexander Kanavin
2022-09-05 18:21 ` [PATCH 2/2] selftest/cases/bblayers.py: build python3-jsonschema only once Alexander Kanavin
2022-09-06 10:20 ` [PATCH 1/2] oe-setup-build: add a tool for discovering config templates and setting up builds John Ogness
2022-09-06 11:24 ` Alexander Kanavin
[not found] ` <171241B5563541EC.6347@lists.openembedded.org>
2022-09-06 11:31 ` [OE-core] " Alexander Kanavin
2022-09-06 12:25 ` Peter Kjellerstedt [this message]
2022-09-06 12:34 ` Alexander Kanavin
[not found] ` <17124592CD5AC7E6.32046@lists.openembedded.org>
2022-09-07 8:57 ` Alexander Kanavin
2022-09-07 9:15 ` Richard Purdie
2022-09-07 9:19 ` Alexander Kanavin
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=6632fb17a872496ea3b7a61a42f2ae06@axis.com \
--to=peter.kjellerstedt@axis.com \
--cc=alex.kanavin@gmail.com \
--cc=alex@linutronix.de \
--cc=john.ogness@linutronix.de \
--cc=openembedded-core@lists.openembedded.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.