On 6/1/20 12:39 AM, Yury V. Zaytsev wrote:
On Sun, 31 May 2020, Matt Billenstein via pypy-dev wrote:
I think if you want to ship portable binary packages, they should be
self-contained - you can't really know what Apple is going to include
or remove from release to release.
I think this principle holds on the various Linux distros as well -
you can't know what version of the various dependencies is going to
be installed.
Well, the principled approach would be to do something like
https://github.com/squeaky-pl/portable-pypy
... only it's a hell a lot of work, and the current package is
"portable enough", so not sure this effort even makes a lot of sense.
|
|
|I think porting the current make_portable to macOS would not be so
terrible. Since most of the work has been done for linux64/linux32, it
is "just" a matter of adjusting the workflow. I opened
https://foss.heptapod.net/pypy/pypy/issues/3240 which only requires
devop-level python skills to fix. Help is welcome.|
|
|
|Matti
|
||
_______________________________________________
pypy-dev mailing list
pypy-dev@python.org
https://mail.python.org/mailman/listinfo/pypy-dev
