Saw your PR here hebisch/poplog#1 (comment)
For a gate of testing, we should test for a few months on a fork, and resubmit upstream (since upstream is very stable).
A bit of background on my fork:
I've spent some time (starting a few years back) trying to sort out the porting process since this was missing from the Internet. I gathered an initial doc: https://github.com/truedat101/poplog/blob/master/PORTING.txt
and then further investigations: truedat101/poplog#4
and then eventually engaged with hebisch to get clarifications, which I captured here: truedat101/poplog#4 (comment)
There is some complexity in bootstrapping, by nature, the corepop. You need a corepop to get started. My goal was to get a port done for raspi5 (aarch64), so I could then port to MediaTek platform for a kids EDU computer project. As I went down this path, I realized a lot of the build infrastructure is very specific to ubuntu, and a bit of a challenge (if we are just talking linux) to maintain. So Docker could solve an ease of getting started problem or making it easy to get into the cloud. I opted to get nix packaging done, so we can easily vendor the corepops and all of the tooling to make a binary. This is done now.
On the new fork, I will maintain going forward, I have 3 ports now and some benchmarks. Please make a PR on https://github.com/IoTone/poplog
I'll try to run this through and see if there are any issues, and otherwise, we can add this as another supported packaging/deployment approach and feature it in the main README. We probably also want to make it podman compatible too.
Saw your PR here hebisch/poplog#1 (comment)
For a gate of testing, we should test for a few months on a fork, and resubmit upstream (since upstream is very stable).
A bit of background on my fork:
I've spent some time (starting a few years back) trying to sort out the porting process since this was missing from the Internet. I gathered an initial doc: https://github.com/truedat101/poplog/blob/master/PORTING.txt
and then further investigations: truedat101/poplog#4
and then eventually engaged with hebisch to get clarifications, which I captured here: truedat101/poplog#4 (comment)
There is some complexity in bootstrapping, by nature, the corepop. You need a corepop to get started. My goal was to get a port done for raspi5 (aarch64), so I could then port to MediaTek platform for a kids EDU computer project. As I went down this path, I realized a lot of the build infrastructure is very specific to ubuntu, and a bit of a challenge (if we are just talking linux) to maintain. So Docker could solve an ease of getting started problem or making it easy to get into the cloud. I opted to get nix packaging done, so we can easily vendor the corepops and all of the tooling to make a binary. This is done now.
On the new fork, I will maintain going forward, I have 3 ports now and some benchmarks. Please make a PR on https://github.com/IoTone/poplog
I'll try to run this through and see if there are any issues, and otherwise, we can add this as another supported packaging/deployment approach and feature it in the main README. We probably also want to make it podman compatible too.