On Tue, 6 Sept 2022 at 14:25, Peter Kjellerstedt <peter.kjellerst...@axis.com> wrote:
> 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? I'd like to keep it within 'oe-setup-..' family though: oe-setup-layers, oe-setup-build, and then later oe-setup as a general integrated one-stop thing that ties it all together: oe-setup kirkstone oe-setup master +docker +systemd oe-setup yoe riscv64 oe-setup webos oe-setup some-custom.json Like RP suggested. I think having discovery functionality in something called 'setup' is actually fine, as the setup actually happens from the available choices, and one would want to know about them first. I'll certainly switch to subcommands; this will allow adding config fragment management as well. Alex
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#170351): https://lists.openembedded.org/g/openembedded-core/message/170351 Mute This Topic: https://lists.openembedded.org/mt/93485066/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
