Re: [bitbake-devel] [PATCH 1/4] bitbake-setup: update vscode workspace always

On Tue, 7 Apr 2026 at 21:58, <[email protected]> wrote:

> Maybe this patch is not very important if bitbake-setup itself does not
> change anymore. Might be that I thought this should be improved when
> working on bitbake-setup itself, which is a very special use case.

What I would like to understand is this: what kind of local changes
require re-generating the vscode workspace (when otherwise there are
no changes in bitbake-setup configuration). Presumably the user does
'something' that causes the workspace to go out of sync, what is it,
can you provide examples? Can we write the workspace in a more
'universal' way such that it doesn't happen?

Alex