Thoughts on pushing the Mentor Graphics setup script improvements to oe-core

NOTES.md

Thoughts on pushing the MEL setup script features upstream

MEL setup-environment features

Likely appropriate for upstream

• Configures local.conf for a given MACHINE
• Configures local.conf for a given DISTRO
• Common underlying layer find mechanism which searches a given path or globs for for layers, to allow the script to add them by name and find the BSP/DISTRO layers
  • Adds the BSP layer and its dependencies to bblayers.conf for a given MACHINE
  • Adds the DISTRO layer and its dependencies to bblayers.conf for a given DISTRO
  • Adds specified layers, by name, to bblayers.conf
  • Adds specified optional layers, by name, to bblayers.conf (non-fatal if missing)
  • Automatically adds dependent layers for any included layers
• Sorts the bblayers in layer priority order (BBFILE_PRIORITY), with support for priority overrides. I already have a bitbake-layers sort-layers plugin to do this.
• Supports per-layer setup script hooks and local.conf snippets
• Supports per-layer machine specific local.conf snippets

Likely not appropriate for upstream

These could likely be done via hooks in meta-mentor.

• Automatic set of MACHINE based on the installed MEL BSP
• Automatic inclusion of layers for hotfixes/updates/customer-specifics

Reference

• OSS Systems - Managing platforms based on the Yocto Project
• wr-lx-setup
• angstrom-setup-scripts
• hopper

TODO.md

• Add support for per-layer hooks and local.conf fragments
  • Consider OSS Systems' python hook capability and EULA handling
• Add new sub-commands to bitbake-layers
• Break out the remaining features and add arguments to the oe-core setup script