New comment by EliteTK on void-packages repository

https://github.com/void-linux/void-packages/pull/33712#issuecomment-995384130

Comment:
Some distros take the self-referential approach of just making pypy depend on itself for every build. Where at some point in the past they had some bootstrap package which was either an upstream binary or a cpython2 build of pypy which was then used to kickstart the ouroboros in perpetuity. Would this be an option? (Apparently, alpine and maybe archlinux did this.)

Alternatively, it's possible to have the pypy package have cpython2 sources in the distfiles instead of the upstream pypy and use that to then have the pypy package first build cpython2 and then pypy. This would avoid having an official cpython2 package and I think this is certainly a lot more transparent than using the upstream pypy.

@dkwo are you still interested in getting this working? If not, I can try to pick up the effort.