I got interested in this recently, seeing what peebee has been doing, with arch32pup and arch64pup. So I had a go in woofQ, to build EasyOS based on Arch packages, see first blog post:
https://bkhome.org/news/202201/hit-road ... yarch.html
I got past that "road block", it turned out to be a minor bump on the road, and have got a desktop working.
I was reading posts in peebee's arch32pup thread, and they report that support for building with Arch packages got removed from woof-CE. Ditto Scientific Linux. I wondered about that, and found that it was done here:
https://github.com/puppylinux-woof-CE/w ... 3e3e7da4e1
I presume that it was discussed beforehand, before doing that.
Although Arch support is still there in the legacy branch, the scripts are old and broken. For example, 0setup needs to be fixed. I have appended mine here, from woofQ, with fixes for importing Arch packages. See attached 0setup with false ".gz" appended.
An argument against build from Arch packages is that it is a rolling release; however, as I explained in my blog post, Arch keeps package snapshots, going back several years. Here is my DISTRO_COMPAT_REPOS-arch-20211231' attached, with false ".gz".
That file has a different syntax from modern woof-CE, but is the same as in woof-CE legacy branch.
My interest in building EasyArch, is can run it in a container in EasyOS Dunfell series, for access to its larger package repository. But, EasyArch could also be released as a standalone product, if people are interested.