Bug 8789 - eSDK: allow disabling devtool subcommands based on capabilities
Summary: eSDK: allow disabling devtool subcommands based on capabilities
Status: NEW
Alias: None
Product: OE-Core
Classification: Build System, Metadata & Runtime
Component: devtools / tool chain (show other bugs)
Version: 2.0
Hardware: All Multiple
: Medium enhancement
Target Milestone: Future
Assignee: Unassigned
QA Contact:
URL:
Whiteboard:
Depends on: 6651
Blocks:
  Show dependency tree
 
Reported: 2015-12-11 01:25 UTC by Paul Eggleton
Modified: 2025-07-03 14:48 UTC (History)
5 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: No (bug/feature does not impact docs)


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Paul Eggleton 2015-12-11 01:25:36 UTC
During ext SDK construction if we know we aren't including the full sstate for the image and SSTATE_MIRRORS isn't set in the local.conf file we've created (after we've generated the final local.conf), we should configure devtool to hide or disable the build-image and package subcommands since they won't be usable.

I'd like to do this in a manner that allows any devtool subcommand to be disabled from devtool's config file; this should let people disable parts of the ext SDK if they feel their users won't need them.
Comment 1 Randy MacLeod 2023-06-29 16:38:24 UTC
Still worth doing when we have the people available. -- YP bug review.