I've tried to package MetaCall with Python support under an OSX-KVM VM using a bash script (build.sh).
This process has been stalled due to multiples issues encountered :
The following command sudo installer -pkg /path/to/package.pkg -target / does not care about the argument given to -target and always installs Python as a system dependency.
Tweaking the rpath of the libraries would throw this error :
A quick search on Google about this error led us to this StackOverFlow answer :
We disabled code signing on a few files of Python and tried again, gave us this error :
We tried to use dtruss to trace system calls but met a bug in DTrace implementation from Apple which is at the moment closed source, and thus cannot be solved directly to understand what is going on.
Hence, after discussion with @viferga and @giarve, we decided to work on Homebrew support so that we can figure out a solution later for this packaging approach.
Next step should be to install python (or any other runtime in its relocatable form), here's some links about relocatable python and ruby distributions:
I've tried to package MetaCall with Python support under an OSX-KVM VM using a bash script (
build.sh
).This process has been stalled due to multiples issues encountered :
The following command
sudo installer -pkg /path/to/package.pkg -target /
does not care about the argument given to-target
and always installs Python as a system dependency.So I tried to package/make portable the system Python following this blog instruction, but ran into another issue, all files from the system Python installation are signed by Apple/Apple developers.
Tweaking the
rpath
of the libraries would throw this error :A quick search on Google about this error led us to this StackOverFlow answer :
We disabled code signing on a few files of Python and tried again, gave us this error :
We tried to use
dtruss
to trace system calls but met a bug inDTrace
implementation from Apple which is at the moment closed source, and thus cannot be solved directly to understand what is going on.Hence, after discussion with @viferga and @giarve, we decided to work on Homebrew support so that we can figure out a solution later for this packaging approach.
Some solutions, we have yet to try :
Future steps
Next step should be to install python (or any other runtime in its relocatable form), here's some links about relocatable python and ruby distributions:
For Ruby support, we might want to use this :