D6846: packaging: script the building of a MacOS installer using a custom python

[mharbison72 (Matt Harbison)]

mharbison72 added a comment.


  In D6846#118733 <https://phab.mercurial-scm.org/D6846#118733>, @marmoute wrote:
  
  > What's the latest with this diff ? It seems to still be a work in progress. Should it be in the "need-review" state?
  
  The hangup here is that the installed code seems to want to look in the path where it was built to load libraries.  I have no idea why.  It would be good if somebody figured out why, because I have a similar problem with the thg build on Mac.  (But unlike here, that's not fatal because it falls back to a library inside the bundle.)
  
  My thought with this was to be able to build an official py2 installer that worked on more than the very latest platform.  But I also thought that we would hang on to py2 for awhile.  If we're not, then this probably isn't worth pursuing, assuming PyOxidizer works out on OS X (so far, so good).  I'm not so excited about dropping py2 because of the amount of work still needed on hg on Windows, thg on Windows and Mac, and the packaging on both.  But 10.16 will remove all builtin python, so something will probably need to be done one way or the other by September or so.

REPOSITORY
  rHG Mercurial

CHANGES SINCE LAST ACTION
  https://phab.mercurial-scm.org/D6846/new/

REVISION DETAIL
  https://phab.mercurial-scm.org/D6846

To: mharbison72, #hg-reviewers
Cc: marmoute, mercurial-devel