Summary: | dev-lang/micropython should become slotted | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Florian Manschwetus <manschwetus> |
Component: | Current packages | Assignee: | No maintainer - Look at https://wiki.gentoo.org/wiki/Project:Proxy_Maintainers if you want to take care of it <maintainer-needed> |
Status: | UNCONFIRMED --- | ||
Severity: | normal | CC: | gentoo, treecleaner |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
URL: | https://github.com/micropython/micropython/releases | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 859289, 859295, 859298 |
Description
Florian Manschwetus
2022-07-19 11:07:54 UTC
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. [I] dev-lang/micropython Verfügbare Versionen: (0) (~)1.11-r1^t (~)1.17^t (ABI-5) (~)1.18^t[1] (ABI-6) (~)1.19^t[1] 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: https://github.com/manschwetus/gentoo-overlay/ Please review and comment |