On Wed, 14 Jan 2026 at 01:03, Otavio Salvador via lists.openembedded.org <[email protected]> wrote:
> 1. pip-installed bitbake-setup Cannot Access Default Registries > > When installing bitbake-setup via pip and running bitbake-setup init, the > command fails because it cannot locate the default registry files that > would normally be at ./bitbake/default-registry/. > > This creates a confusing first experience for users who expect a > pip-installed tool to work out of the box. Having to clone the full BitBake > repository defeats the convenience of pip installation. > bitbake-setup in pip is known to be broken and not ready. Please do not try to use it until it has an announcement and a place in the official documentation. We put it there just to avoid someone else squatting on the pypi project name, and that required uploading 'something'. I worried even then that users will find the package and make assumptions about using it, and now it happened. > 3. Unclear Error When Using Non-Raw URLs > > When running bitbake-setup init with a URL to a .conf.json file hosted on > platforms like GitHub or GitLab, users naturally copy the URL from their > browser. This URL points to an HTML page rather than the raw JSON content, > causing the command to fail. > > The error message does not clearly indicate that a raw/plain URL is > required. A clearer error message or guidance would help users understand > the issue more quickly. > This shouldn't be difficult to fix. Can you propose a patch? > 4. Tool to Generate Templates from Existing Environments > > Currently, there is no way to generate a BitBake Setup Template from: > > - An existing BitBake Setup Instance > - A traditional workspace set up manually with oe-init-build-env > - Any working Yocto/OpenEmbedded build environment > > A tool to export a working environment as a template would: > > - Help users migrate existing projects to the new bitbake-setup > workflow > - Make it easier to share working configurations with colleagues or > the community > - Reduce the barrier to adoption for users with established projects > > This might be harder than you think. Making a config template from an existing bitbake-setup driven build (with an empty local.conf) is not hard, but converting legacy setups requires decomposing local.conf into fragments, giving them correct names and placing them into correct layers, something that only a human can do well. Or the tool can try to do it half-way: put local.conf/bblayers.conf into a openembedded template into some layer, and then generate a bitbake-setup with oe-template entry in it. But that in itself is legacy; fragments and empty local.conf are the future. For converting established projects the best feasible option might be to write migration guidelines. > > > 5. Fragment Discovery on OpenEmbedded Layer Index > > The OpenEmbedded Layer Index (https://layers.openembedded.org) is an > excellent resource for discovering layers. However, there is no equivalent > discovery mechanism for configuration fragments. > > Adding a tab or section for fragments would help users discover available > fragments and understand what problems they solve. > Yes, this would be a useful addition. > ------------------------------ > > We hope this feedback is helpful. We are happy to discuss any of these > points further or assist with documentation improvements. > Certainly very useful, thanks for writing it up, those are perspectives and points that I wouldn't be able to come up with. The only issue I don't quite understand yet is "allow empty variants in templates". Alex
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#229363): https://lists.openembedded.org/g/openembedded-core/message/229363 Mute This Topic: https://lists.openembedded.org/mt/117264857/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
