D7450: packaging: add support for PyOxidizer

[mharbison72 (Matt Harbison)]

mharbison72 added a comment.


  In D7450#118095 <https://phab.mercurial-scm.org/D7450#118095>, @indygreg wrote:
  
  > 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.
  
  Yeah, these were a few of the things we talked about.  I think we're all on the same page here, and I'm hoping for a single executable.  Martin mentioned early in the IRC chat, maybe putting the files under /etc/mercurial/templates (which is fine now that Windows has a global area for hg data), but then we'd minimally need an HGRCPATH analog for templates for running tests.
  
  The other tricky thing that came up is maybe teaching %include how to include resources.  At work, we point to a custom map-cmdline file that includes the default one, and then overrides just enough so that `hg log -v` will put each file on a newline, instead of making them space delimited.
  
  > 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.
  
  I thought about adding a user level search path, but it will probably get complicated to tell resource based vs user file based files when reading without adding a known prefix to the resource names.  So I set that aside, because I'm not sure how useful it would actually be for users to install templates.

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, mharbison72
Cc: marmoute, mharbison72, martinvonz, durin42, kevincox, mercurial-devel