Thanks! The library we wanted to install this time was `xattr`, which has this line: https://github.com/xattr/xattr/blob/master/xattr/lib_build.py#L5. How do you recommend working around that? Do we simply need to install it in the file system instead of bundling it in the binary?
On Wed, Jun 17, 2020 at 8:30 PM Gregory Szorc <gregory.sz...@gmail.com> wrote: > Yeah, you'll want a pyoxidizer.bzl that installs hg and other stuff. Using > PythonDistribution.pip_install() ( > https://pyoxidizer.readthedocs.io/en/stable/config_api.html#pythondistribution-pip-install-args-extra-envs) > with arguments to process a requirements.txt file is likely how I'd do it. > > Sadly, PyOxidizer doesn't (yet) support including another config file. > That seems like a reasonable feature request. Although I'm unsure if the > Rust Starlark implementation can handle it. Can you please file a feature > request against PyOxidizer? > > Another missing feature that would make this easier would be injecting > environment variables into pyoxidizer.bzl files. That way we could teach > Mercurial's canonical pyoxidizer.bzl to inject other install rules via > presence of environment variables. That would make things easier to extend. > We could potentially also accept command line arguments to `pyoxidizer > build` to inject additional variables into the Starlark context. Again, > please file feature requests here! > > Since you have a bit more resources than the average user and you are > probably opinionated about how your binaries are built, you might want to > look into bypassing PyOxidizer and doing the resource packaging yourself. > See > https://pyoxidizer.readthedocs.io/en/latest/oxidized_importer_freezing_applications.html > and https://pyoxidizer.readthedocs.io/en/latest/rust.html for more on > this topic. > > On Wed, Jun 17, 2020 at 4:56 PM Augie Fackler <r...@durin42.com> wrote: > >> We're working on a PyOxidizer Mercurial for our users, and we want to >> bake some extra stuff beyond just hg (evolve, some in-house stuff) into the >> binary. Should we be making our own pyoxidizer.bzl that installs hg and >> whatever else we need? Is there a way we could reuse the bits in the >> existing configuration? >> >> Thanks! >> Augie > >
_______________________________________________ Mercurial-devel mailing list Mercurial-devel@mercurial-scm.org https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel
