As micropython has diffrent mpy file format versions, it should become slotted, based on ABI level.
- 1.12 to 1.18 is ABI 5
- since 1.19 is ABI 6
micropython gets installed in a single version, currently ABI 5
micropython is available in all supported ABI versions
Based on this ebuilds for mpy-cross-v5 and mpy-cross-v6 could be added, to complete micropython development support.
I would vote for piking up naming scheme also for the micropython binary, as well as the mpy-cross binary. So it would become "micropython-v6" for example.
I got ebuilds for 1.18 and 1.19 prepared, following this ideas, I'll try to push them later the day.
(0) (~)1.11-r1^t (~)1.17^t
Now I will also re-add mpy-cross, also following this scheme, then I can depend on with dev-python/mpy-cross-v5 and dev-python/mpy-cross-v6.
Which in turn should allow to get a dev-python/pybricksdev package, so if this runs we have also a first verification of this work.
Ok I think my work is ok now, as it is sufficient to run pybricksdev. So I'll check how I can upload it, likely I'll start a personal overlay. So I can put in all I did to get pybricksdev running. Then responsible devs can review make suggestions and cherry pick for the official tree as desired.
I created a personal overlay with the ebuilds as described:
Please review and comment