D7450: packaging: add support for PyOxidizer

[indygreg (Gregory Szorc)]

indygreg added a comment.


  I don't have strong opinions about bundling templates and other resources internally versus externally. I do think it would be cool to have a fully self-contained executable. But that would require a command to write out embedded resources to the filesystem so people can modify them. That's a bit obscure.
  
  We may want a policy-like primitive to control where to load resources by default. And/or we can establish a clear order for resolution. e.g. try CLI argument, environment variable, then config option, then user directory, then global directory, etc.
  
  On Windows (which is where we have the biggest pressing concern for PyOxidizer at the moment since we aren't producing Python 3 installers yet), it doesn't much matter since the installer can install multiple files easily. I think installing files next to the executable mimicking today's install layout is the path of least resistance.

REPOSITORY
  rHG Mercurial

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

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

To: indygreg, #hg-reviewers
Cc: marmoute, mharbison72, martinvonz, durin42, kevincox, mercurial-devel