How to get back to a one-file `hg` executable?

[Augie Fackler]

Hi Greg!

I'm working on updating hg and trying to switch us to pyoxidizer for
Windows, but a speedbump on the way is that our Mac builds have broken:
we'd been relying on the one-file build mode of the binary, and now that
appears to be impossible? Am I missing something? I tried editing the
pyoxidizer.bzl to make all resources be "in-memory" but then I get a
failure trying to add the hg packages, eg:

error[PYOXIDIZER_BUILD]: resource collector does not allow resources in
filesystem-relative
  --> ./pyoxidizer.bzl:64:5
   |
64 |     exe.add_python_resources(exe.pip_install(["--verbose", ROOT]))
   |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
add_python_resources()

which left me stumped. Am I missing something obvious in the docs or
configuration that would let us get back to one-file executables for our
macOS users?

Thanks,
Augie
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.mercurial-scm.org/pipermail/mercurial-devel/attachments/20201102/a78def8a/attachment.html>