Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

moulin: layers not removed from bblayers.conf when removed from manifest #90

Open
sa-kib opened this issue Nov 16, 2023 · 2 comments
Open

Comments

@sa-kib
Copy link
Contributor

sa-kib commented Nov 16, 2023

Steps to reproduce:

  • fill layers: section of manifest with sample layer names, e.g.:
[..]
layers:
        - "poky/meta"
        - "poky/meta-poky"
        - "poky/meta-yocto-bsp"
        - "meta-virtualization"
[..]
  • generate bblayers.conf, e.g.:
$ ninja conf-dom0
  • observe above layers in bblayers.conf, e.g.:
$ cat yocto/build/dom0/conf/bblayers.conf
[..] 
BBLAYERS ?= " \
  [..]/yocto/poky/meta \
  [..]/yocto/poky/meta-poky \
  [..]/yocto/poky/meta-yocto-bsp \
  [..]/yocto/meta-virtualization \
[..]
  • remove some layer from layers: section of manifest, e.g.:
[..]
layers:
        - "poky/meta"
        - "poky/meta-poky"
        - "poky/meta-yocto-bsp"
 [..]
  • re-generatate bblayers.conf:
$ touch yocto/build/dom0/conf/local.conf
$ ninja conf-dom0
  • observe removed layer still present in Yocto configuration, e.g.:
$ cat yocto/build/dom0/conf/bblayers.conf
[..] 
BBLAYERS ?= " \
  [..]/yocto/poky/meta \
  [..]/yocto/poky/meta-poky \
  [..]/yocto/poky/meta-yocto-bsp \
  [..]/yocto/meta-virtualization \
[..]
  • only after one manually removes file bblayers.conf & re-generates configuration it starts to reflect manifest changes

So since bitbake-layers add-layer only seems to be able to add layers, but not remove already added ones, we probably can remove bblayers,conf and start afresh each time configuration is updated.

@lorc
Copy link
Collaborator

lorc commented Dec 12, 2023

Fixed via #94

@lorc lorc closed this as completed Dec 12, 2023
@lorc
Copy link
Collaborator

lorc commented Jan 24, 2024

The fix was reverted via #98, because it introduced an issue that seriously impaired day-to-day work.

@lorc lorc reopened this Jan 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants