Bug 8789

Summary: eSDK: allow disabling devtool subcommands based on capabilities
Product: [Build System, Metadata & Runtime] OE-Core Reporter: Paul Eggleton <bluelightning>
Component: devtools / tool chainAssignee: Unassigned <unassigned>
Status: NEW --- QA Contact:
Severity: enhancement    
Priority: Medium CC: alexandru.c.georgescu, jose.perez.carranza, meta.mr.watcher, meta.watcher, randy.macleod
Version: 2.0   
Target Milestone: Future   
Hardware: All   
OS: Multiple   
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: No (bug/feature does not impact docs)
Bug Depends on: 6651    
Bug Blocks:    

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.