Closed jeremysinger closed 4 months ago
hi @kwitaszczyk Duncan suggested that you might prefer us to name this package micropython-cheri since it is a specific fork of the original micropython which runs ok in hybrid mode. Our code has not been upstreamed to the official micropython repo.
@jeremysinger Yes, we briefly discussed this yesterday. You can either duplicate code under a -cheri port but it would be preferable to create a port that reuses the upstream port with some modifications. You can have a look at devel/gdb and devel/gdb-cheri (https://github.com/CTSRD-CHERI/cheribsd-ports/pull/130) for suggestions how to do that. However, it might turn out that the upstream and -cheri ports differ significantly and then it wouldn't make sense to reuse the upstream port.
hi @kwitaszczyk yes we will change the name to micropython-cheri. I had a chat with @djlowther and we reluctantly decided that we can't keep constant track of upstream micropython due to its frequent commits and possible divergence.
hi @kwitaszczyk we changed the package name to micropython-morello since our MicroPython fork hasn't been tested on RISC-V at all.
hi @kwitaszczyk thanks for your advice today at CHERITech 24 workshop. I have tidied up the pull request - removing unnecessary history. Hope this is ok now.
@jeremysinger I remember we discussed simplifying this port not to duplicate logic already existing in lang/micropython. Is that something you want to do, or would you prefer to land this as is at the moment?
hi @kwitaszczyk is the new commit message ok? I tried to follow your instructions
hi @kwitaszczyk is the new commit message ok? I tried to follow your instructions
It looks much better. Thank you! I have added a few comments to make the port/package more user-friendly.
MicroPython builds for purecap CheriBSD