Ralf

The usecase I've in mind is to substitute all dependencies from a reference to build a additional `multiPackage` which needs all the existings dependencies + the a additional package from...

> Taking a step back: what is the actual motivation of having Bob managing the layers? What is the benefit of adding this feature compared to git submodules? I think...

> The current situation is that when a layer is updated, the whole team must be notified about this to update their local gitsubmodule(s). Sometimes it is forgotten and the...

> Nevertheless, it would be a nice feature when the main recipes are on a branch and there are new changes on it you can you can get a notification...

I pushed some updates to the code to avoid the internal package.. It's still not ready for review... Anyway - after some internal discussions we think that merging the (sub-)...

The idea was to have more control about the layers. e.g. if a common sublayer is used by 2 different layers one might need to use the newer layer spec....

I've implemented something like this in a small plugin. It uses the gitlab API to create the tags and is highly customised to our needs. State is something between "works...

I've to correct myself. I did not implement this in a plugin - it's just a simple shell-script using `bob query-scm`. [create_tags.sh.gz](https://github.com/BobBuildTool/bob/files/15145013/create_tags.sh.gz) , replaces the git-URLs with the https ones...