Hello,
Apologize for no response for long months.
The similar discussion is now happening again in a thread [0].
However, I’m still not sure how it’s worth to move our current target (buster on warrior) to dunfell.
See my old post [1] for more about the reasons.
The porting is definitely possible and it makes sense from the perspective of
longer term maintenance of resources in OE-Core layer.
On the other hand, I confirmed that not a few recipes (including some core components like python)
need to be adjusted again for newer recipes in dunfell and it would take several months at least
for updating and testing recipes.
Also, there are more gaps between package versions of buster and dunfell,
which pulls additional conflicts in their features / specifications.
If more motivations for the porting become clear, I would like to look at more details,
otherwise warrior would keep being the base for buster packages in this project.
[0] https://github.com/meta-debian/meta-debian/issues/191
[1] https://github.com/meta-debian/meta-debian/issues/191#issuecomment-860219822
Regards,
Kazu
--
You received this message because you are subscribed to the Google Groups "DEBY" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
meta-debian...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/meta-debian/915564d7-eae7-4231-8baa-1ee2695886c6n%40googlegroups.com.