Using autogen in all branches is not a solution. To autogen an ebuild it's a pretty cool because permit to be updated but doesn't ensure that the updated package will be yet compilable.
So, we need to create a new tool that permit to analyze the generated kits from the autogen branch and later create a PR with the update ebuild after an automatic testing pipeline.
These are the key activities to do:
1) integrate the reposcan feature over the anise-portage-converter tool in order to have an easy and fast way to generate the reposcan JSON file to use for identify the packages to update. The reposcan generates the cache data files used by metatools that are with the struct visible here. Having the JSON cache file will permits to easily analyze the trees and identify the new packages.
2) the new merge tool must create a PR with the new ebuild but to have a way to maintain the previous ebuild too in order to have a way to mask a fresh ebuild if something is broken.
3) we need a new tool that help to cleanup the distfiles files no more needed.
4) after that a PR is merged an automatic trigger must to update the meta-repo of the target branch in order to automatically point to the new GIT hash
Using
autogenin all branches is not a solution. To autogen an ebuild it's a pretty cool because permit to be updated but doesn't ensure that the updated package will be yet compilable. So, we need to create a new tool that permit to analyze the generated kits from the autogen branch and later create a PR with the update ebuild after an automatic testing pipeline. These are the key activities to do: 1) integrate thereposcanfeature over theanise-portage-convertertool in order to have an easy and fast way to generate the reposcan JSON file to use for identify the packages to update. Thereposcangenerates the cache data files used by metatools that are with the struct visible here. Having the JSON cache file will permits to easily analyze the trees and identify the new packages. 2) the new merge tool must create a PR with the new ebuild but to have a way to maintain the previous ebuild too in order to have a way to mask a fresh ebuild if something is broken. 3) we need a new tool that help to cleanup the distfiles files no more needed. 4) after that a PR is merged an automatic trigger must to update the meta-repo of the target branch in order to automatically point to the new GIT hash